Merge expanding into workflow automation

Moving from unified APIs into workflow automation would push Merge up the stack from plumbing to decision making. Today Merge helps software companies connect to HR, CRM, ticketing, accounting, and file systems through one normalized API. A workflow layer would let customers not just pull data from those systems, but route approvals, trigger follow ups, and update records across them without writing custom backend logic.

• Merge and Zapier sit at different starting points. Merge sells to software teams that need product integrations to work the same way across many apps. Zapier sells a workflow builder to end users and teams, with thousands of app connections, multi step automations, and usage based pricing. That means Merge would be moving toward Zapier’s use case, not just its market category.
  1 sacra 2 sacra 3 sacra
• The hard part is not drawing boxes in a workflow builder. It is owning authentication, data mapping, sync reliability, custom fields, and edge cases inside each app. Merge already does much of that infrastructure work. That gives it a credible base for automation, because the workflow layer is strongest when the underlying data model is already normalized and maintained.
  1 sacra 4 sacra
• The closest comparison is not pure no code automation, but platforms like Workato and Alloy that combine integration infrastructure with workflow logic. Workato built a large enterprise business around low code recipes, while Alloy describes universal APIs as good for basic read and write use cases but says customers graduate to workflow engines when they need configurability and logic.
  3 sacra 4 sacra

If Merge adds workflow tooling, the likely path is embedded automation for SaaS vendors first, then broader business process automation later. That would deepen product stickiness, raise revenue per customer, and put Merge in a stronger position as software buyers increasingly expect apps to connect and act, not just exchange data.