Zapier's growth threatens partner control

This tension revealed that integrations were becoming part of product ownership, not just distribution. As Zapier grew into the place where users discovered apps, configured workflows, and compared alternatives, partners got reach but lost control over onboarding, usage data, and how their product was presented. That made Zapier useful for the long tail, but risky around the handful of integrations that shaped activation, retention, and upsell.1 2 3

• A partner could join Zapier to claim hundreds of integrations quickly, but the user often had to leave the app, open a Zapier account, map fields by hand, and manage the workflow in a second interface. For common jobs like alerts, syncing contacts, or updating records, many SaaS teams saw a native in app flow as categorically better.1 2 3
• The conflict was also about information and merchandising power. Partners described Zapier collecting workflow data without sharing enough usage detail back, while also surfacing alternative apps on integration pages. Once Zapier sat between the customer and many similar tools, it could make those tools look interchangeable.1 3
• That pressure created room for embedded integration infrastructure like Prismatic, Paragon, and Merge. These products sell the rails for building integrations that look native inside a SaaS product, so the app keeps the customer relationship while still avoiding the cost of writing every connector from scratch.1 2 4 5

The market keeps moving toward a split model. SaaS companies will build their most used integrations themselves, or with embedded infrastructure, because those flows drive activation and retention. Horizontal automation platforms will still matter, but more of their value will concentrate in the long tail, in cross app orchestration, and in use cases where no single vendor wants to build the connection first.2 3 4 5