Zapier as Customer-Facing Gatekeeper

This tension revealed that Zapier had stopped being just plumbing and had become a customer facing gatekeeper. Once users started discovering apps on Zapier, comparing alternatives there, and setting up key workflows in Zapier instead of inside the app itself, partners risked losing product control, usage data, and the chance to make their own integrations feel native and sticky.

• Partners got reach from Zapier, but they also sent users into a separate workflow builder. That meant users left the partner product, created a Zapier account, configured automations in a generic interface, and often never saw the partner's own preferred paths or messaging around which integrations mattered most.
  1 sacra 2 sacra
• The conflict sharpened because Zapier could surface substitute apps alongside partners and did not share much usage data back. For a SaaS company, that data is the map for deciding which 10 or so integrations to build in house, where native UX can remove friction and keep customers inside the product.
  1 sacra 2 sacra 3 sacra
• This is why tools like Tray.io and later embedded integration products mattered. They let SaaS companies use integration infrastructure behind the scenes, so the customer clicks a native button inside the app instead of bouncing out to Zapier. Zapier keeps the long tail, while first party teams reclaim the head.
  1 sacra 2 sacra 5 sacra 6 sacra

The market is moving toward a split model. SaaS companies will keep building native integrations for the handful of workflows that drive onboarding, activation, and retention, while platforms like Zapier remain valuable for everything else. The companies that win will be the ones that own the in product experience and use middleware only where customers do not need to see it.