Merge Expanding Into Workflow Automation
Merge
The important shift is from being a plumbing layer that moves data, to becoming the place where business logic lives. Merge already handles authentication, data normalization, syncing, and monitoring across HR, ATS, CRM, ticketing, accounting, and file storage systems, which is most of the hard groundwork for automation. Once that layer is in place, adding a visual workflow builder is a natural way to capture more of the customer’s daily operating workflow and budget.
-
Universal APIs like Merge are strongest when a customer wants one clean schema and quick read and write access across many apps. The handoff point into workflow automation comes when customers want branching logic, approvals, custom field mapping, and user configurable actions. That is where platforms like Alloy and Workato move higher into the stack.
-
The competitive path is visible in the market. Workato built a large business by packaging connectors, a low code builder, and reusable recipes for functions like HR, finance, IT, and sales ops. Merge already has the connector layer and common model, so the missing piece is the workflow surface that lets non engineers orchestrate those integrations.
-
Going upmarket also pushes Merge in this direction. In enterprise accounts, integrations stop being simple field syncs and become tenant specific processes with custom objects, permissions, rate limits, and exception handling. A workflow product can expose that complexity as configuration instead of custom code, which makes Merge more valuable and harder to replace.
The next stage of the category is likely a blend of unified API, configurable workflow, and deeper observability. If Merge adds automation on top of its existing integration fabric, it can evolve from a fast implementation tool for product teams into a broader operating layer for enterprise software, with more expansion revenue per customer and a much larger role in day to day business processes.