The first question is where the work happens. Teams wiring together cloud apps should compare Zapier, Make and n8n, from easiest to most technical; Microsoft 365 shops should start with Power Automate; IT departments integrating core systems at scale should look at Workato; companies with old desktop software that has no API need RPA from UiPath or Power Automate; and departments that mostly route requests for approval are better served by Kissflow, Pipefy, Nintex or Process Street. Price a real workflow on each shortlisted tool, since billing units differ so much, and test what happens when a step fails before you trust it with customer data. The FAQ below explains those billing units, when RPA is worth it and the terms for self-hosting n8n.
What counts as a task, a credit or an execution?
Each platform bills a different unit, so the same automation can cost very different amounts. Zapier counts a task for each successful action, while triggers, filters, paths, failed steps and, in its newer Zaps, formatting, loops and branching are free. Make bills credits, which replaced operations in August 2025: by default every module run costs one credit, including each check a scheduled trigger makes for new data, and some AI apps use more. An n8n execution is one run of a whole workflow, however many steps it has, and Power Automate licenses people and robots instead, allowing 40,000 actions a day per Premium user and 250,000 per Process license. A ten-step workflow that runs 1,000 times a month therefore uses 1,000 n8n executions, about 9,000 Zapier tasks if its nine steps after the trigger are all actions, and at least 10,000 Make credits, because the trigger’s checks count too.
When do you need RPA instead of an app connector?
Use connectors whenever the applications involved have them. Robotic process automation, in Microsoft’s definition, is for applications that lack a prebuilt connector and have no API to build one with: a software robot copies a person’s mouse movements and keystrokes, which makes it the tool for terminal emulators, old desktop systems and websites without integrations. Attended bots run on a person’s computer while that person works, and unattended bots sign into a machine on their own, run the flow and sign out, which is why Microsoft and UiPath price them separately. Screen-based robots can break when an application’s layout changes, which is why UiPath sells self-healing UI automation in its Enterprise plan, so keep RPA for the systems you cannot connect any other way.
Can we self-host n8n for free?
For internal use, yes. The software is distributed under n8n’s Sustainable Use License, which allows you to use and modify the software only for your own internal business purposes or for non-commercial and personal use, and a standard self-hosted version is published on GitHub; files marked as enterprise code need a paid license. The license does not let you distribute n8n to others for a fee, and n8n’s license FAQ says a commercial agreement is needed to host it as a service or let people outside your organization build workflows on your instance. Self-hosting also makes security your job: in January 2026 a critical flaw rated 10.0, CVE-2026-21858, let attackers take over unpatched instances without logging in until version 1.121.0 fixed it. Activepieces, a smaller rival, uses the MIT license outside its enterprise folders.