The best workflow automation tools for teams without developers

Prices and features checked: 2026-11-09. Prices in the currency the vendor shows, checked on the date shown; we do not convert.

How we compared them

Eight workflow automation platforms, compared for teams that have no developer on staff and need to connect the tools they already use: forms, CRMs, spreadsheets, chat, invoicing. Every row above was built from the vendor's own pricing page as read on 2026-11-09; where a page shows no price we print "see pricing" or "quote only" rather than a figure from memory or from a third-party listing. Make's price grid did not render in the text we could read, so Make carries no prices on this page.

Our criteria, in the order we weight them for small teams:

1. Billing unit and what it does to the bill. Per task, per operation, per run, per user or per credit. The unit matters more than the headline price once a workflow has more than two steps; our Zapier vs Make vs n8n page computes the same workflow across three units.
2. Entry paid price and free plan, as published, with the billing interval stated.
3. Governance: single sign-on, audit logs and role-based permissions, and which plan they first appear on. Most comparison pages ignore this; it is the difference between a team tool and a personal one.
4. EU data residency, as stated on the pricing page or linked FAQ. "Not stated" means exactly that; several vendors publish region information in separate trust documentation we did not read today, and GDPR compliance is not the same as EU hosting.
5. AI steps and agent features, and how they are billed.
6. Connector breadth and depth, where the vendor gave a figure on the page we read.

Five of the eight (Zapier, Make, n8n, Pipedream and IFTTT) sell to small teams directly. Three (Power Automate, Workato, Tray.ai) are included because teams inside larger organisations inherit them. Zapier, Make and n8n have affiliate programmes, which we have not joined; the ordering and verdicts do not depend on that, and tools without a programme get the same columns.

Why teams automate: the problem framing

Two vendor surveys from 2025 describe the pressure, and both are vendor research on general workforces rather than independent studies. Microsoft's Work Trend Index, combining a 31,000-person survey with Microsoft 365 telemetry, estimates that employees are interrupted about every two minutes by meetings, emails or pings, around 275 times across a day that includes off-hours activity B^[10]. Atlassian's State of Teams survey of 12,000 knowledge workers puts time spent searching for information at about a quarter of the week B^[11]. Workflow automation addresses the part of both problems that is mechanical: the notification that exists only to tell a human to copy a value from one system into another.

The market that sells the fix is large and its size is disputed. Mordor Intelligence values workflow automation at USD 23.77 billion in 2025, growing to USD 40.77 billion by 2031 at 9.41 percent a year; other analysts' snippets run two to three times higher for 2030 C^[9]. We cite the figure for scale only.

Decision table by company size

You are	Start with	Why	Watch for
A solo operator automating consumer apps, smart devices or a side business	IFTTT Free or Starter (USD 2.09 per month billed annually) [8]	Cheapest credits; all features on the free plan; hourly polling	Business connectors are thin; no governance
A freelancer or two-person company with a handful of business automations	Zapier Free, then Professional at USD 19.99 per month billed annually for 750 tasks [1]	Largest connector library and the shortest learning curve	Each action step is a task; multi-step Zaps get expensive at volume
A team of 2 to 10 with branching logic and tens of thousands of runs	n8n Cloud Starter (EUR 20 per month billed annually, 2,500 executions) or Pro (EUR 50, 10,000) [3]; Make if you prefer a scenario canvas and can read the current grid yourself [2]	n8n bills per run regardless of steps and hosts in the EU; Make's credits are per module	n8n's node editor assumes some technical comfort
A team of 10 to 50 with one technical person	n8n Pro, or self-hosted n8n on your own server; Pipedream Startup (USD 99 per month billed annually) if that person writes code [5]	Project roles arrive on n8n Pro; Pipedream gives code steps and MCP access	Self-hosting costs hours, not licence fees; Pipedream's Free tier is development only
50 to 250 people with IT, compliance and a budget for a quote	Workato [6] or Tray.ai [7]; n8n or Zapier Enterprise for custom terms [1][3]	SSO, RBAC and audit features are standard on these editions	No published prices; annual commitments
Any size on Microsoft 365 with Dataverse or SharePoint at the centre	Power Automate Premium at USD 15 per user per month paid yearly [4]	Native to the Microsoft stack; per-user billing suits predictable team sizes	No permanent free plan on the pricing page; per-bot RPA plans at USD 150 to 215 a month
Any size that must keep data in the EU	n8n hosted (Frankfurt) or self-hosted [3]; Workato's EU region [6]; Tray.ai regional hosting on Enterprise [7]	These are the vendors whose pages state a region	Others may offer it; it was not stated where we looked

Pricing models compared

Tool	Billing unit	Entry paid price (checked 2026-11-09)	Free plan
Zapier	Task: one successful action step; MCP and programmatic calls also count	Professional USD 19.99 per month billed annually (USD 29.99 monthly) for 750 tasks; 2,000 tasks USD 49 annual; Team from USD 69 annual for 2,000 tasks [1]	100 tasks a month, two-step Zaps, 15-minute polling
Make	Credit: one module operation; routers and error handlers free	see pricing; the grid did not render for us on 2026-11-09 [2]	1,000 credits a month
n8n	Execution: one run of the whole workflow regardless of steps	Starter EUR 20 per month billed annually (2,500 executions); Pro EUR 50 (10,000); Business EUR 667 (40,000, self-hosted only) [3]	Cloud trial of 1,000 executions; self-hosted Community Edition free
Power Automate	Per user (cloud flows) or per bot (unattended RPA)	Premium USD 15 per user per month paid yearly; Process USD 150 per bot per month; Hosted Process USD 215 [4]	30-day trial only
Pipedream	Credit: 30 seconds of compute; USD 0.012 per extra credit	Startup USD 99 per month billed annually (USD 150 monthly), 10,000 credits, 100 external users included [5]	Development only, no production runs
IFTTT	Credit: one applet run, AI feature or MCP call	Starter USD 2.09 per month billed annually (USD 25.08 a year), 5,000 credits; Pro USD 5.49, 20,000; Pro+ USD 13.99, 100,000 [8]	1,000 credits a month, unlimited applets, hourly polling
Workato	Task consumption, with concurrency limits per edition	Quote only [6]	Trial only
Tray.ai	Tasks and Helix Compute Units; no per-user fees	iPaaS quote only; Tray Helix "starts at USD 50 a month" [7]	30-day trial with 1 million tasks

The unit decides the bill. A five-step workflow run 10,000 times a month is 30,000 Zapier tasks, roughly 50,000 Make credits, and 10,000 n8n executions. Per-user pricing (Power Automate) is indifferent to volume and punishing for a small team running many flows per person. Credits priced in compute time (Pipedream) reward fast steps and penalise waiting on slow APIs. Before comparing headline prices, count the steps in your three most common workflows and multiply.

Connectors and depth

Breadth figures change monthly and vendors count differently, so we report only what we read today: Pipedream lists more than 3,000 connectors across all tiers ^[5]; IFTTT gives all services on every plan including Free ^[8]; Zapier does not put a connector count on its pricing page, and its library is widely regarded as the largest, which we state as reputation rather than measurement ^[1]. Depth matters more than breadth for a small team: the question is whether the connector for your CRM exposes the trigger you need (new deal moved to stage X) rather than only the generic ones (new record). Test that in the free tier before you pay. n8n and Pipedream let you fall back to a raw HTTP request when the connector is shallow; Zapier and Make do too, with more clicks; IFTTT and Power Automate's standard connectors are the most constrained.

AI steps and agents

Every vendor now sells AI steps, and the billing differs. Zapier bills AI steps and MCP calls from the task pool, with higher-tier models consuming more ^[1]. IFTTT draws AI features and MCP usage from the same credit allowance as applet runs ^[8]. Pipedream exposes MCP access on all tiers, including Free for development ^[5]. Make's FAQ describes credits as the unit for AI actions as well ^[2]. Workato names two of its editions after MCP (Business MCP, Enterprise MCP) ^[6], and Tray.ai sells Helix and a Merlin Agent Builder with guardrails and audit logs alongside its iPaaS ^[7]. n8n's pricing page bills AI nodes as part of an execution like any other step ^[3].

Two cautions. First, an agent step that can call tools is a step whose cost you cannot predict from the diagram; cap retries and set budgets. Second, the automation-bias literature is consistent: people over-trust automated output and check it less, and the effect is reduced by training and accountability rather than eliminated A^[12][13]. An automation that writes to a customer-facing system should have a human review step until its error rate is measured, however good the demo looked.

Governance: SSO, audit logs, permissions

Tool	Single sign-on	Audit log	Roles and permissions
Zapier	SAML SSO on Team and Enterprise; SCIM Enterprise	6 months on Team, 1 year on Enterprise	Folder permissions on Team; advanced admin permissions and workspaces on Enterprise [1]
Make	Not stated on the pricing page [2]	Not stated	Not stated
n8n	SSO and LDAP on Business (self-hosted) and Enterprise	Enterprise only	Admin roles, project editors and instance admins from Pro; custom roles Enterprise [3]
Power Automate	Not on the pricing page; Microsoft Entra handles identity for the suite	Not stated; "managed environments" listed as included [4]	Not stated on the pricing page
Pipedream	Business only; SCIM Business only	Not stated	Not stated [5]
IFTTT	Not stated	Not stated	Not stated [8]
Workato	SAML SSO and MFA on Standard	Activity audit on Enterprise MCP; log retention 30 days (Standard) or 90 days (Enterprise MCP)	Role-based access control on Standard [6]
Tray.ai	Enterprise; add-on on Team	Audit trails on all plans	Not stated [7]

For a team of five, the practical floor is "who can edit this workflow and who can see the credentials it uses". n8n Pro and Zapier Team are the cheapest plans where that question has an answer. Below those tiers you are sharing one login, which is acceptable for a sole trader and a liability for anyone handling customer data.

EU data residency

Only three of the eight pricing pages say where data lives. n8n's FAQ states that hosted plans store data in the EU on servers in Frankfurt, and self-hosting puts location entirely in your hands ^[3]. Workato's site exposes an EU login region (app.eu.workato.com), although its pricing page does not describe EU hosting as a feature ^[6]. Tray.ai lists regional hosting as an Enterprise feature and an add-on on Team, without naming the EU ^[7]. Zapier, Make, Power Automate, Pipedream and IFTTT make no residency statement on the pages we read ^{[1][2][4][5][8]}; Pipedream lists SOC 2 Type 2 and GDPR, which concern controls and legal basis, not location.

If a contract or a data-protection officer requires EU hosting, the shortlist today is n8n (hosted or self-hosted), Workato's EU region and Tray.ai Enterprise, and for a Microsoft shop, Power Automate with the tenant's region confirmed in Microsoft's own documentation rather than assumed. For everyone else, ask the vendor in writing; "not stated on the pricing page" is a gap in our reading, not a finding that the option does not exist.

Power Automate for Microsoft shops

If your organisation runs Microsoft 365, Power Automate is probably already available to you in some form, and its economics differ from every other tool here. The pricing page lists Premium at USD 15 per user per month paid yearly, Process (unattended RPA) at USD 150 per bot per month and Hosted Process at USD 215, with a Process Mining add-on at USD 5,000 per tenant per month for Premium customers; the only free option shown is a 30-day trial ^[4]. Per-user pricing means a team of eight running fifty flows pays the same as a team of eight running five. Standard connectors cover the Microsoft stack well; premium connectors and HTTP steps require the paid plan. For a team whose data already lives in SharePoint, Dataverse or Dynamics, it is the default choice; for a team whose data lives in Google Workspace, HubSpot and Slack, it is rarely the cheapest or the simplest.

Estimate your automation ROI

Before choosing a platform, estimate whether the workflow is worth automating at all. A simple model:

Monthly value = (minutes saved per run × runs per month ÷ 60) × loaded hourly cost of the person doing it today Monthly cost = platform fee + (hours to build ÷ 12) × hourly cost + monthly maintenance hours × hourly cost

A workflow that saves four minutes, runs 500 times a month and replaces work by someone costing EUR 40 an hour is worth about EUR 1,330 a month; at that volume it costs about EUR 20 a month on n8n Starter, about USD 89 on Zapier at three tasks per run, and nothing beyond the licence on Power Automate Premium if the person already has it. A workflow that saves four minutes and runs ten times a month is worth EUR 27 and is not worth building on any platform unless the error it prevents is expensive. Our business process automation guide covers how to find the workflows worth the effort, and our n8n workflow templates page has worked examples of the common ones.

What to do next

Count the steps and runs of your three most frequent manual hand-offs, then run them through the tool finder, which filters these platforms by billing unit, governance needs, EU hosting and the apps you must connect, and returns a shortlist with the current prices. If your shortlist comes down to the three usual names, the Zapier vs Make vs n8n comparison prices the same workflow across all three at 1,000, 10,000 and 100,000 runs.

Frequently asked questions

What is the best workflow automation tool for a small business?

For a team under ten without a developer: Zapier if you value the connector library and simplicity and run a few light automations (Professional USD 19.99 per month billed annually for 750 tasks); n8n Cloud if you run thousands of multi-step runs or must keep data in the EU (Starter EUR 20 per month billed annually for 2,500 executions). Prices as read on 2026-11-09 ^[1][3].

What is the difference between Zapier, Make and n8n pricing?

The billing unit. Zapier counts each successful action step as a task, Make counts each module operation as a credit, and n8n counts one execution per run of the whole workflow regardless of steps ^[1][2][3]. A five-step workflow costs five units on Zapier, roughly five on Make and one on n8n. Our Zapier vs Make vs n8n page works through the numbers.

Which workflow automation tools store data in the EU?

Of the eight pricing pages we read on 2026-11-09, only n8n states it plainly: hosted plans store data in Frankfurt, and self-hosting leaves the location to you ^[3]. Workato exposes an EU login region and Tray.ai offers regional hosting on Enterprise without naming the EU ^[6][7]. The others make no statement on their pricing pages, which is not the same as not offering it; ask in writing.

Is Microsoft Power Automate free with Microsoft 365?

The pricing page lists only a 30-day free trial and paid plans: Premium at USD 15 per user per month paid yearly and per-bot RPA plans from USD 150 a month ^[4]. Some Microsoft 365 licences include limited Power Automate rights for standard connectors; the pricing page does not spell them out, so check your licence terms rather than assuming.

Do I need an audit log for workflow automation?

If a workflow touches customer or financial data, yes: you need to know who changed it and when. On the plans we read, audit logging first appears on Zapier Team (6 months), Workato Enterprise MCP and n8n Enterprise; Tray.ai lists audit trails on all plans ^[1][3][6][7]. Below those tiers, keep the number of editors to one and document changes yourself.

How do I calculate the ROI of automating a workflow?

Multiply minutes saved per run by runs per month, convert to hours and multiply by the loaded hourly cost of the person doing it today. Subtract the platform fee, the build time spread over a year and monthly maintenance. Workflows that run hundreds of times a month almost always pay; workflows that run ten times a month rarely do unless they prevent an expensive error.

Sources and evidence

1. Zapier pricing (plans, task tiers, task definition, SSO and audit log rows) — Zapier (2026), vendor page A zapier.com/pricing (retrieved 2026-11-09)
2. Make pricing page (FAQ text only; price grid not rendered) — Make (Celonis) (2026), vendor page B www.make.com/en/pricing (retrieved 2026-11-09)
3. n8n pricing (plans, execution definition, EU hosting FAQ, SSO and audit rows) — n8n GmbH (2026), vendor page A n8n.io/pricing/ (retrieved 2026-11-09)
4. Power Automate pricing — Microsoft (2026), vendor page A www.microsoft.com/en-us/power-platform/products/power-automate/pricing (retrieved 2026-11-09)
5. Pipedream pricing — Pipedream (2026), vendor page A pipedream.com/pricing (retrieved 2026-11-09)
6. Workato pricing (editions and features; no prices published) — Workato (2026), vendor page B www.workato.com/pricing (retrieved 2026-11-09)
7. Tray.ai pricing (iPaaS editions, Helix, trial; no iPaaS prices published) — Tray.ai (2026), vendor page B tray.ai/pricing (retrieved 2026-11-09)
8. IFTTT plans — IFTTT (2026), vendor page A ifttt.com/plans (retrieved 2026-11-09)
9. Workflow Automation Market Size and Share — Mordor Intelligence (2026), report C www.mordorintelligence.com/industry-reports/workflow-automation-market (retrieved 2026-11-09)
10. 2025 Work Trend Index Annual Report: The year the Frontier Firm is born — Microsoft WorkLab (2025), report B www.microsoft.com/en-us/worklab/work-trend-index/2025-the-year-the-fro (retrieved 2026-11-09)
11. State of Teams 2025 — Atlassian (2025), report B www.atlassian.com/blog/state-of-teams-2025 (retrieved 2026-11-09)
12. Complacency and Bias in Human Use of Automation: An Attentional Integration — Parasuraman, R.; Manzey, D. H. (2010), review A doi.org/10.1177/0018720810376055 (retrieved 2026-11-09)
13. Automation bias: a systematic review of frequency, effect mediators, and mitigators — Goddard, K.; Roudsari, A.; Wyatt, J. C. (2012), systematic review A doi.org/10.1136/amiajnl-2011-000089 (retrieved 2026-11-09)