Automation and integration tools are for businesses where the same information gets typed twice: a form fills a spreadsheet, someone copies it into the CRM, someone else pastes it into an invoice. The choice usually goes wrong on ambition. Teams start with a workflow that spans six apps and branches three ways, it breaks silently in week two, and nobody notices until a customer does. The automations that survive are boring, single-step, and cover work that happens every day.
How to choose
Does it connect your actual apps?
Catalogue size is marketing; what matters is whether the two or three systems you depend on are supported, and how deeply. A connector that reads records but cannot update them will send you back to manual work halfway through the job.
How is usage counted?
Most of these charge by task, operation or run rather than by seat, and a workflow that fires on every row can burn a monthly allowance in an afternoon. Filter early, before the expensive step, and check how the vendor counts a failed run.
Who fixes it when it breaks?
Automations fail quietly when an app changes a field or a token expires. Someone needs to own error notifications and know how to replay a run. If that person does not exist, keep the workflows simple enough that a failure is obvious.
No-code, low-code or self-hosted?
Ready-made recipes suit simple, common jobs. Visual builders with routers and filters handle real branching but take a weekend to learn. Self-hosting adds control and data residency, and adds a server you now maintain.
The tools in this category
- Zapier — best at connecting the widest range of apps quickly; suits teams who value coverage, but usage is billed per task.
- Make — best at branching scenarios with routers and filters; suits small teams willing to learn a real builder.
- n8n — best at self-hosted workflows mixing visual nodes with code; suits technical operators who want control over data.
- Integrately — best at switching on ready-made recipes without building; suits simple jobs between mainstream apps.
- Pabbly Connect — best at cutting recurring automation cost, with a lifetime licence option; suits cost-conscious small teams.
- IFTTT — best at light if-this-then-that rules across apps and devices; suits sole traders and very small teams.
- Workato — best at connecting core business systems through low-code recipes; suits larger organisations with IT support.
- Tray.io — best at governed integration across enterprise systems and AI agents; suits teams with a named owner and quoted pricing.
What to watch out for
- Task-based pricing that scales with volume, not headcount. A busy form or a chatty webhook can multiply the bill without anyone changing a setting.
- Silent failures. Without alerting and a habit of checking run history, a broken workflow can lose a fortnight of leads before anyone spots it.
- Automating a bad process. If the manual steps are messy, automation just makes the mess faster and harder to see. Fix the process first.
- Key-person risk. Complex scenarios built by one person, with no notes on why a filter exists, become untouchable the day they leave.
Questions people ask
What should we automate first?
The dullest thing you do daily that has one trigger and one outcome, such as putting new enquiries in one place. Reliability builds trust; clever workflows do not.
Is a cheaper platform a false economy?
Not necessarily, if it supports your apps. The real costs are rebuilding after an outgrown limit and losing time to a thin connector, so test your hardest workflow during the trial.
Do we still need automation if our tools already integrate?
Often not. Native integrations between two systems are usually more reliable than a third-party bridge. Reach for these tools when the built-in link is missing or too rigid.
See the full, always-current list on the automation and integration tools page.