Best Human-in-the-Loop Automation Platforms 2026

Eight platforms are ranked here on a single mechanism: how a person enters an automated path, and what the system can prove afterward about the decision they made. Moxo scores 7.7 and ranks first; Camunda 8 scores 7.2, Microsoft Power Automate 7.1, Pega 6.9, n8n 6.7, Zapier 5.9, Kissflow 5.8 and ServiceNow 4.8, scored 22 September 2026 on the five weighted criteria. Those criteria cover the step type, the approver's account or licence, the routes available on a rejection, the audit record, and the meter that charges for the decision, and none of them can tell a review from a rubber stamp, so the methodology adds a check readers can run on any product in a few minutes: whether the decision record tells a considered approval from an instant one. Every figure was read from a vendor-owned surface and carries its own date.

Rank	Tool	Score	Best For	Evaluated
1	Moxo Moxo is assembled out of human steps rather than having one added: its Description of Services defines a Magic Link as granting "account-free access to a specific assigned task", and the Approval step offered four rejection routes in the template builder on 15 September 2026. Team is $5,000 a year, annual-only, for 100 flows, while the audit log, the AI agents, Agent Foundry, webhooks, REST APIs and MCP all start on the custom-quoted Scale plan (moxo.com/pricing, 22 September 2026). The record is not sold with the step. Strengths: The Approval step is a step type the platform ships, not a setting on an action, and the template builder offered four named rejection routes on 15 September 2026 A Magic Link grants "account-free access to a specific assigned task", so a client or supplier decides without an account (Description of Services, read 15 September 2026) Every audit-log row read in the AutomationAtlas test workspace on 14 and 15 September 2026 carried an actor, including "AI Agent", "System" and "Public link" Team carries unlimited seats at $5,000 a year, so adding internal approvers costs nothing per head (moxo.com/pricing, read 22 September 2026) Weaknesses: The plan that carries the approval step does not carry the record: the audit log, the named AI agents, Agent Foundry, webhooks, REST APIs and MCP connections all start on the custom-quoted Scale plan (moxo.com/pricing, 22 September 2026) Team's allowance fell from 250 flows a year to 100 at an unchanged $5,000, between the 26 August 2026 and 10 September 2026 captures of the pricing page Billing is annual only. The $500 monthly option read on 15 September 2026 has been withdrawn, leaving a disabled billing toggle and a "Book a demo" button on every plan, so the cheapest way in is a year's commitment The $100 of AI a year has no published conversion to the credits the product logs against a flow, so allowance and consumption cannot be reconciled from public pages	7.7	Teams whose decisions sit with clients or suppliers who will never hold a licence	Sep 24, 2026
2	Camunda Camunda 8's human step is the BPMN user task, a primitive of the engine itself rather than an app added to a flow, and it takes the only 10 on this list for how the human enters the path. Who may act is the counterweight. Tasklist V2 no longer evaluates candidate users or candidate groups for task visibility or assignment. Camunda publishes no plan price, and self-managed production requires an Enterprise licence (camunda.com/pricing, read 21 September 2026). Strengths: The BPMN user task is a primitive of the engine rather than an added app, so the process waits by definition instead of by configuration (docs.camunda.io, read 21 September 2026) BPMN 2.0 is a published standard, so rejection paths and timer escalations stay readable outside the vendor's own tooling Local development is free and Camunda 8 SaaS carries a 30-day trial, so the mechanism can be tested before a sales conversation (camunda.com/pricing, read 21 September 2026) Camunda 8 Self-Managed runs on the buyer's own Kubernetes, which keeps tasks and their history inside infrastructure the team controls (docs.camunda.io, read 21 September 2026) Weaknesses: Tasklist V2 no longer evaluates candidate users or candidate groups for task visibility or assignment, so who can see and take a task is no longer settled by the model alone (Camunda 8.9 release notes, read 21 September 2026) No plan price is published: free local development, a 30-day SaaS trial and an Enterprise licence for self-managed production leave a cost per decision point that cannot be modelled from public pages (camunda.com/pricing, read 21 September 2026) The documented path assumes the approver already holds an identity in the platform	7.2	Engineering teams modelling long-running processes in BPMN, where every approver already holds an identity	Sep 24, 2026
3	Power Automate Power Automate's approval is a standard connector action. Microsoft states that "any license that grants access to Power Automate and the ability to use standard connectors is sufficient to create approval flows", and Premium is $15.00 per user per month paid yearly. Copilot Studio agent flows meter separately at 13 Copilot Credits per 100 agent flow actions, and the decision record splits across Dataverse and Purview (14 September 2026). Strengths: Approvals ride a standard connector, and Microsoft states that any licence granting Power Automate access and standard connector use "is sufficient to create approval flows" (learn.microsoft.com, 14 September 2026) Premium is $15.00 per user per month paid yearly, a published figure a buyer can model against a seat count (microsoft.com, 14 September 2026) Copilot Studio documents multistage and AI approvals in agent flows as a supported pattern rather than a custom build (learn.microsoft.com, read 21 September 2026) Approval activity is retrievable through both Dataverse and Purview audit, so the record survives outside the flow's own run history Weaknesses: Copilot Studio agent flows meter separately in Copilot Credits, at 13 per 100 agent flow actions with capacity sold at $200.00 per 25,000-credit pack per month, so the approval a buyer already owns and the agent approval they pay for run on different meters Once prepaid Copilot Credit capacity is exhausted, new agent flow runs are blocked. A credit shortfall stops the approval instead of adding an overage line The decision record splits across Dataverse and Purview rather than sitting in one approval log, so reconstructing a single decision means two surfaces Microsoft's own approvals page states "There are four approval types you can use" directly above a table with five rows (ms.date 29 April 2026)	7.1	Organisations already licensed for Microsoft 365 and Power Automate standard connectors	Sep 24, 2026
4	Pega Platform Pega's Approve/Reject is a named case lifecycle step, and Directed Web Access issues an external assignment whose link "does not require login". That route needs an administrator-provisioned External operator, and it is unavailable on Constellation. AWS Marketplace lists Workflow Automation at $162,000.00 a year to 120,000 cases, then $1.35 per case beyond the allowance (read 21 September 2026). Strengths: Approve/Reject is a named step in the case lifecycle, not a toggle on an action (docs.pega.com, read 21 September 2026) Directed Web Access issues a single-use external assignment whose link "does not require login", and Pega's licence compliance page classifies those people as Invocation users rather than named users (docs.pega.com, read 21 September 2026) Escalation for an incomplete assignment is documented and configurable, so a stalled decision has a defined timer path (docs.pega.com, read 21 September 2026) Pega is the only platform here with a published per-case rate card: $162,000.00 a year to 120,000 cases at $1.35 per case beyond it, rising to $1,188,000.00 a year to 1,000,000 cases at $1.19 (AWS Marketplace, read 21 September 2026) Weaknesses: Directed Web Access needs an External operator that an administrator must set up before the login-free link works, and it is unavailable on Constellation The published rate card meters the case, not the decision. A process carrying four approvals and one carrying a single approval draw down the same allowance at the same speed Case history documents its fields as a date, type, user ID and memo per instance, with no published retention period beside it (read 21 September 2026) The lowest published tier is $162,000.00 a year, a six-figure floor that puts evaluation out of reach for a single department	6.9	Regulated enterprises already running case management at six-figure case volumes	Sep 24, 2026
5	n8n n8n carries the cheapest meter in this ranking: Cloud Starter is 20 euros a month billed annually for 2,500 executions, and the self-hosted Community Edition carries no licence fee (n8n.io/pricing, 14 September 2026). The human-in-the-loop step reaches an approver across nine notification channels. What it brings back is thinner, because the tool-review decision is binary and by default the node's output records only "approved" and a timestamp. Strengths: Cloud Starter is 20 euros a month billed annually for 2,500 executions, the cheapest published meter in this ranking (n8n.io/pricing, 14 September 2026) The self-hosted Community Edition carries no licence fee, so the gate can run with no vendor invoice at all The human-in-the-loop step reaches an approver across nine notification channels, so the decision arrives where the approver already works (docs.n8n.io, read 21 September 2026) The meter is the execution rather than the decision. Adding a second approval to a workflow does not add a second charge Weaknesses: Leave the approver list empty and anyone who can see the message can approve, so the gate is only as strong as the channel it was posted to By default the node's output records only "approved" and a timestamp, which shows that a decision happened but not who made it The tool-review decision is binary, with no send-back-for-revision and no named rejection branch, which is why decision routes score 4 out of 10	6.7	Technical teams running their own workflows, where the approver is a known colleague on a trusted channel	Sep 24, 2026
6	Zapier Zapier documents an edit-before-approve path, letting a reviewer change the data before the run continues. It also states that "Only successful Human in the Loop actions will count toward your task usage". The same help page offers a reviewer type of "Anyone", defined as "members outside of your Zapier account", and states under Limitations that "Reviewers must have a Zapier account" (help.zapier.com, read 21 September 2026). Strengths: The Human in the Loop step documents an edit-before-approve path, letting a reviewer change the data before the run continues (help.zapier.com, read 21 September 2026) Zapier states that "Only successful Human in the Loop actions will count toward your task usage", so a pending or abandoned decision is not billed (read 21 September 2026) Professional is $19.99 a month billed annually, a published figure a buyer can model against the approval gate Human in the Loop also collects data rather than only a yes or no, so one pause can gather what the process was missing (help.zapier.com, read 21 September 2026) Weaknesses: Zapier's own help page contradicts itself: it offers a reviewer type of "Anyone", defined as "members outside of your Zapier account", and states under Limitations on the same page that "Reviewers must have a Zapier account" and that one who lacks one "will be prompted to create a new account" (read 21 September 2026) The approval gate starts on Professional and the audit log on Team. The plan carrying the decision and the plan carrying the record are not the same plan Human in the Loop "is a premium app on Zapier" and requires a paid Zapier account, so the gate starts on a paid plan (read 21 September 2026)	5.9	Small teams gating an existing Zap where every reviewer can hold a Zapier seat	Sep 24, 2026
7	Kissflow Kissflow publishes its portal audit field list in full, recording an Actor, a Platform and an IP address per event. The approver is what that record costs. Portal users consume licences, and Kissflow states that "If there's a shortage of licenses, the invited user will remain inactive and unable to sign in to the portal". No plan price is published (read 21 September 2026). Strengths: The portal audit log publishes its field list in full, recording an Actor, a Platform and an IP address per event (community.kissflow.com, read 21 September 2026) More than 200 pre-built process templates cover approval-shaped work including purchase requests, expense approvals and vendor registration (kissflow.com, read 17 September 2026) Kissflow's pricing page states "No surcharges for AI or API usage", so the meter does not fork when AI is added to a step (read 21 September 2026) Fixed annual agreements mean the decision itself carries no per-unit charge once the contract is signed (kissflow.com/pricing, read 21 September 2026) Weaknesses: Approvers consume portal licences, and Kissflow states that "If there's a shortage of licenses, the invited user will remain inactive and unable to sign in to the portal", so an outsider's ability to decide depends on a seat pool (community.kissflow.com, read 21 September 2026) No plan price is published: kissflow.com/pricing offers "Pricing built around the value you receive" and "Fixed annual agreements", so a cost per decision point cannot be read off a page (read 21 September 2026) Only the portal audit log enumerates its fields. The process audit log is referenced without a published field list (read 21 September 2026)	5.8	Mid-market process owners who need a named, IP-stamped record and can licence every approver	Sep 24, 2026
8	ServiceNow ServiceNow ties for the top decision-record score here: four dedicated AI agent tables make an agent's own working queryable inside the customer's instance, under the customer's own retention. None of it is priced. The external role that lets an outsider approve from the customer portal carries a licence according to vendor-hosted community material, and no price is published for any of the relevant SKUs (servicenow.com/docs, read 21 September 2026). Strengths: Four dedicated AI agent tables store an agent's own working, so the record is queryable in the instance rather than read out of a vendor console (servicenow.com/docs, read 21 September 2026) Because those tables sit in the customer's own instance, retention follows the customer's rules rather than a vendor's log window An outsider can approve a change request or registration request from the customer portal, a documented path rather than a custom build (servicenow.com/docs, read 21 September 2026) The approval and the ITSM, HR or CSM record it gates share one data model, so the decision and the work it governs stay queryable together Weaknesses: Vendor-hosted community material reports that the external role letting an outsider approve carries a licence cost, so reaching a person outside the company likely means paying for them No price is published for any of the relevant SKUs: the ITSM pricing page carries a single "Get Custom Quote" call to action per package, which is why cost per decision point scores 2, the lowest in this ranking Rejection handling on the documented portal path is an approve or reject decision on a request rather than a set of named return destinations, which is why decision routes score 4 out of 10	4.8	ServiceNow customers keeping the decision record inside their own instance	Sep 24, 2026

Methodology

Eight platforms scored on how the human enters the path (25%), what the approver must have (20%), decision routes (20%), decision record (20%) and cost per decision point (15%), from vendor-owned surfaces read on the dates stated. Process control depth and agent construction are deliberately out of scope and scored on separate pages. Positions follow total score.

Read full methodology

What this ranking scores

A human-in-the-loop step has two jobs that pull against each other. It has to be easy enough that the right person acts within the hour, and strict enough afterwards to prove who acted. One decision settles both: whether your approver needed an account. The eight platforms here answer it in four different ways.

Moxo's Description of Services defines a Magic Link as a link granting "account-free access to a specific assigned task", and the audit log in the AutomationAtlas test workspace labels that actor "Public link" rather than a name (read 15 September 2026).

Zapier puts both halves of the problem on the same help page. The Request Approval step's reviewer type can be set to "Anyone", which Zapier defines as "members outside of your Zapier account", while the Limitations section below states that "Reviewers must have a Zapier account" and that a reviewer who lacks one "will be prompted to create a new account" (help.zapier.com, read 21 September 2026).

Kissflow turns the same decision into a licence counter. Its portal documentation states that "If there's a shortage of licenses, the invited user will remain inactive and unable to sign in to the portal" (community.kissflow.com, read 21 September 2026).

Pega documents a fourth shape and then prices it. Directed Web Access issues an external assignment where "The link in the external Assignment does not require login, but the user can use it only once", and Pega's licence compliance page books those people as "processing performed by Web users (typically through the Directed Web access feature), classified as Invocation users" rather than as named users (docs.pega.com, read 21 September 2026).

Reaching a person and enrolling one are different acts. A comparison table treats them as the same feature. The currency changes each time, from friction to a seat to the strength of the name in the log, and Pega is the only vendor here that puts a licence class on the difference. This ranking scores that mechanism across five weighted criteria and nothing else.

The category boundary

This page scores the pause and what survives it. It does not score process control depth (retries, incidents, compensation and state management), which is scored on Best Process Orchestration Platforms 2026. Building the agent is out too: the model, the tool catalogue and the reasoning loop are scored on Best AI Agent Platforms 2026.

Camunda 8 shows why the boundary sits there. Its BPMN user task is the most first-class human step in this list and scores accordingly, while the durable engine underneath it, which is the reason most teams shortlist Camunda at all, is scored nowhere on this page.

The five criteria

Each platform was scored from 1 to 10 on five weighted criteria, with the total a weighted average carried to one decimal.

How the human enters the path (25%)

Whether the pause is a step type the platform ships, or an app, node or toggle added to an automation designed to run without stopping. Scored on where the control lives in the builder's own object model, read from vendor documentation or from the builder itself. The line that decides the score is whether the engine can finish the process without a person: an element the engine must wait on scores above a step type the product merely ships, and both score above a switch somebody has to remember to turn on. A 10 is a wait-for-human element that is the workflow engine's own primitive, so the engine cannot execute the process without pausing on it, as a BPMN user task is. A 9 is a named step type the product ships and the engine waits on by definition, such as a Moxo Approval step or a Pega Approve/Reject step. A 4 is a per-tool setting called "Require approval before running" that ships switched off, where the product's default behaviour is to act without asking.

What the approver must have (20%)

The account, licence or seat the deciding person needs before the approve button works, and whether somebody outside your company can act without one. Scored on primary vendor statements about accounts and licences, not on marketing claims about external collaboration. The distinction that sets the score is between reaching a person and enrolling them: a notification reaches any inbox, while a licence gate can leave an invited approver unable to sign in at all. A 9 is a time-limited link scoped to one task with no account behind it. A 3 is an approver who consumes a platform licence from a finite pool. A route that skips the login but still needs an administrator to provision the person scores in the middle.

Decision routes (20%)

What the process can do when the answer is no: send back for revision, let the approver choose the return point, run a designated rejection branch, end the run, reassign, or escalate on a timer. Scored on the named routes a builder can select, counted from vendor documentation or from the builder's own controls, rather than on what could be modelled with enough effort. A 9 offers four or more distinct named outcomes plus a timed escalation path. A 4 offers approve and deny, where deny cancels the action and informs the caller.

Decision record (20%)

What the log stores about a completed decision: whether the actor resolves to an identifiable person, which fields accompany the entry, how far back it can be retrieved, and which plan carries it. Scored on published field lists and retention figures, with plan gating recorded, because an audit log a buyer cannot reach on the plan that carries the approval step is not evidence of anything. The lookalike to separate here is the run log: a run log shows that a step completed, an audit log names who completed it. An 8 publishes the full field list including the actor. A 4 is a stated commitment to auditability with no published fields.

Cost per decision point (15%)

The meter that runs when a person is asked to decide: per flow, per task, per seat, per credit, or nothing extra on a licence you already hold. Scored on published prices only, naming the cheapest plan that carries the approval step, because that is the number a buyer has to model. No published price is scored as no published price rather than as an unknown that might turn out cheap, and a published price a buyer can model scores above silence even when the number is large. A 9 is a supported approval gate at no incremental cost on a licence already in the estate. A 2 is a platform publishing no price for any plan.

On the weighting

The weighting decides the top of this list. How the human enters the path at 25 percent, together with what the approver must have at 20 percent, rewards a platform assembled out of human steps with an account-free route for outsiders, which is why Moxo places first on a cost per decision point score of 4 out of 10, a figure three platforms here beat outright.

Move cost per decision point to 0.30 and how the human enters the path to 0.10, leaving the other three untouched, and the top of the table reorders: n8n takes first at 7.0, Moxo falls to a tie for second with Microsoft at 6.9, Zapier climbs to fourth at 6.2, and Pega and Camunda 8 tie for fifth at 6.1. Neither weighting is more correct in the abstract, and the weights here were fixed before any score was entered. This page weights the mechanism because the mechanism is the question it exists to answer, and a reader whose binding constraint is the invoice should read the cost per decision point scores rather than the totals.

An approval step proves someone was asked, not that anyone decided

Every platform on this list can show that a person was asked, and none of the five criteria tests whether that person weighed anything before saying yes. In our view that gap is what human-in-the-loop has to mean now: once an agent drafts the thing being approved, the failure to fear is not a missing step but a reviewer who approves what the machine wrote without reading it.

The EU AI Act names the tendency. Article 14(4)(b) requires that the people assigned to oversee a high-risk AI system be enabled "to remain aware of the possible tendency of automatically relying or over-relying on the output", which it calls "automation bias" (artificialintelligenceact.eu mirror, read 23 September 2026). A log built to answer "who approved?" cannot speak to that. What speaks to it is the interval between the item reaching the reviewer, or being opened, and the decision landing, together with how often the reviewer changes or refuses what they are shown.

You can test for it in a few minutes on any product you can get an approval step running in. Approve one test item after reading it properly and a second the instant it arrives, then export the decision record and see whether anything in it tells the two apart. If nothing does, the product can prove that a person was asked but not that anyone looked, and a year of approvals landing seconds after assignment, none edited and none refused, will read in that log exactly like a year of careful review. This is a practitioner's check rather than a sixth criterion, and it moves no score on this page.

What a decision point costs

Approval gates are metered on at least five incompatible bases, and no vendor reconciles its meter against anyone else's. The published figures, each against the cheapest plan that carries the gate:

Microsoft Power Automate: approvals ride a standard connector, and Microsoft states that "any license that grants access to Power Automate and the ability to use standard connectors is sufficient to create approval flows", which includes Office 365 licences carrying Power Automate rights. Premium is $15.00 per user per month paid yearly. Copilot Studio agent flows meter separately, at 13 Copilot Credits per 100 agent flow actions, with capacity sold in packs of 25,000 Copilot Credits at $200.00 per pack per month (learn.microsoft.com and microsoft.com, 14 September 2026).
Zapier: the Human in the Loop prerequisites are "A paid Zapier account" and the note that it "is a premium app on Zapier", with Professional at $19.99 a month billed annually. Zapier states that "Only successful Human in the Loop actions will count toward your task usage" (read 21 September 2026).
n8n: the meter is the execution rather than the decision. Cloud Starter is 20 euros a month billed annually for 2,500 executions, and the self-hosted Community Edition carries no licence fee (n8n.io/pricing, 14 September 2026).
Moxo: the meter is the flow. Team is $5,000 a year for 100 flows and $100 of AI a year with unlimited seats, and the audit log, the AI agents, Agent Foundry, webhooks, REST APIs and MCP all start on the custom-quoted Scale plan (moxo.com/pricing, 22 September 2026). The $500 monthly option read here on 15 September 2026 has been withdrawn, leaving a disabled billing toggle and a "Book a demo" button on every plan, so the cheapest way into Moxo is a year's commitment.
Pega: the meter is the case, and the list price is published on AWS Marketplace rather than on pega.com. Workflow Automation is $162,000.00 a year for up to 120,000 cases with $1.35 per case beyond the allowance, rising to $1,188,000.00 a year for up to 1,000,000 cases at $1.19 per case (read 21 September 2026). It is the only per-case rate card in this ranking, and the only six-figure floor.
Camunda 8, Kissflow and ServiceNow: no plan price is published. Camunda offers free local development, an Enterprise licence for Self-Managed production and a 30-day SaaS trial before a sales conversation. Kissflow's pricing page offers "Pricing built around the value you receive", "Fixed annual agreements" and "No surcharges for AI or API usage" (read 21 September 2026).

Three meters deserve a second look before a contract. Moxo's $100 of AI a year has no published conversion to the credits its product logs against a flow, so an allowance and a consumption figure cannot be reconciled from public pages. Microsoft's is stricter: once prepaid Copilot Credit capacity is exhausted, new agent flow runs are blocked, which turns a credit shortfall into a stopped approval rather than an overage line. Pega's counts cases, not decisions. A process carrying four approvals and a process carrying one draw down the same allowance at the same speed.

Considered and not scored

Relay.app is excluded because the product is gone. Its own shutdown notice set deletion of paid accounts and all associated data after Monday 14 September 2026 at 23:59 PT. Its documentation had described the most complete edit-before-approve path any vendor here published, letting a reviewer approve the output as it stood, end the run, "Manually edit/override the AI output", or re-prompt the model. Teams moving off it should read What should teams do now that Relay.app is shutting down?
Make was not scored because its Human in the loop app is not generally available. Make's own app documentation describes it as "currently in closed beta" and limited to invited customers on the Enterprise plan (read 14 September 2026).
Pipefy fits this boundary, since guest users act inside a process without an account and plans count admins and members rather than guests. It sits outside this edition's scored set.
Salesforce Agentforce records generative AI audit data in Data 360, including accept, regenerate, modify and decline actions, and is a genuine fit for this category. It also sits outside this edition's scored set.
Temporal, Prefect, Apache Airflow and Windmill are durable execution engines and are scored on Best Durable Workflow Engines for Production in 2026.
Lindy, CrewAI, Tines and Bardeen build or host agents rather than gating them, and are scored on Best AI Agent Platforms 2026.
SuiteDash, Clinked, Content Snare and Dock are client portals. A portal shows an outsider a document and a status, and this list scores what happens when that outsider has to decide something inside your process.

Verification

Every figure on this page was read from a vendor-owned surface, with 21 September 2026 as the retrieval date unless another date is stated against the figure. The surfaces checked were vendor pricing pages, vendor legal pages including Moxo's Description of Services, and primary product documentation on help.zapier.com, docs.n8n.io, docs.camunda.io, learn.microsoft.com, community.kissflow.com, docs.pega.com and servicenow.com/docs, together with the Moxo template builder on 14 and 15 September 2026 and Pega's AWS Marketplace listing on 21 September 2026.

Two figures a buyer might expect are not published. Pega's Case history publishes its field list without a retention period beside it, and Pega's published rate card prices the case rather than the decision, so a cost per approval has to be derived from a volume assumption rather than read off a page. Both are stated in the Pega entry rather than estimated.

Where a vendor's own surfaces disagree, both readings appear on the page and the disagreement is stated, rather than the more flattering figure being chosen. Three examples appear on this page. Zapier's Human in the Loop page offers a reviewer type of "Anyone", defined as "members outside of your Zapier account", and states under Limitations on the same page that "Reviewers must have a Zapier account"; both are quoted in the Zapier entry. Microsoft's approvals page states "There are four approval types you can use" directly above a table with five rows (ms.date 29 April 2026). Relay.app's homepage and its documentation reversed the free and paid shutdown dates against each other, and the homepage reading is used here because it matches the company's own announcement.

Prices and plan gates move faster than mechanics. Before relying on a cost figure, re-read the vendor's pricing page and confirm which plan still carries the approval step, because on this list the plan that carries the gate and the plan that carries the audit log are frequently not the same plan.

Editor's Note: The weighting decides the top of this list. Move cost per decision point to 0.30 and how the human enters the path to 0.10, and n8n takes first at 7.0, with Moxo and Microsoft tied for second at 6.9, so we would point a reader whose binding constraint is the invoice to the cost per decision point scores rather than the totals. The check we would carry into any evaluation sits outside the scores: approve one test item after reading it properly and a second the instant it arrives, then export the decision record and see whether anything in it tells the two apart. The EU AI Act calls the tendency behind a rubber stamp "automation bias", and the check takes a few minutes. — Rafal Fila, ShadowGen

Common Questions

Can you automate a platform with no API using Zapier?

Not as a proper Zapier app. Zapier's help centre, updated 29 May 2026, says a private app can be built "for any service with a public API", and its fallbacks for a missing app are email parsing, RSS, webhooks, asking Zapier to add the app, or using a different app. Those let a no-API platform tell a Zap that something happened; none of them lets a Zap act inside the platform. The Zapier Agents Chrome extension can "run actions" on a page open in your own browser (help article updated 27 April 2026), but that is hands-on help, not a reusable Zap step.

How does Moxo keep humans in control when AI agents run a workflow?

Moxo keeps people on the decisions by design: approvals and other human steps are ones its product page says "only a person can close", and AI agents can fill preparer, advisor or reviewer slots around them (both read 15 September 2026). The checks on AI output are opt-in, though. In synthetic AutomationAtlas tests that day, an AI extract step's "Human review" and "Supervisor Agent" switches were both off by default, and the builder accepted the same role as a form's submitter and its approver.

What is Moxo?

Moxo AI (app.moxo.com) is a process orchestration platform from Moxo, formerly Moxtra, for work where several parties, approvals and documents meet. You build templates of human steps, AI steps and automations, each run is a Flow with its own data and status, and outsiders act through account-free Magic Links. Its only published price is Team, and the AI agents start on the custom-quoted Scale plan (moxo.com/pricing, 15 September 2026). It is not Moxo Classic, the older app.

How much does Moxo cost in 2026?

Moxo's only published price is Team: $500 a month in the monthly view or $5,000 a year in the yearly view, for 100 flows and $100 of AI a year with unlimited seats (moxo.com/pricing, 15 September 2026). Scale (500 flows and $500 of AI a year) and Enterprise are custom quotes. There is no free plan, no published overage rate and no stated trial length, and the dollar AI allowance has no published conversion to the credits Moxo's product logs.

Related Guides

comparison

Moxo vs Kissflow in 2026: What an Outside Approver Costs, and What the Record Proves

Moxo and Kissflow both sell approvals to people who do not write code, and each wins one round outright: Moxo's Web and Headless SDKs run the approval inside the buyer's own product, under the buyer's own sign-in. Kissflow's portal audit log stamps every event with an actor, a device and an IP, where Moxo publishes no field list. Both answers are quoted, not priced, and both meters punish a one-step request sent to hundreds of clients. Cost, the decision record, rejection routes, AI metering and governance, verified 14 to 23 September 2026.

comparison

Moxo vs Camunda 8 in 2026: BPMN User Tasks for Staff, Step Types for Outsiders

Camunda 8 can fix a process under cases already running, since active instances migrate onto a corrected definition and, for Camunda user tasks, "a migrated active user task remains assigned to the same user". Moxo keeps the shared queue that Camunda's Tasklist V2 stops evaluating, with desks that are "a shared inbox that multiple users can pick work from". Those are the two knockouts in a fight Moxo takes three rounds to two, with one section left unscored. Portability, AI review gates and a published price decide the rest, verified 14 to 23 September 2026.

comparison

Moxo vs n8n in 2026: Who Runs the Engine and Who Keeps the Record

n8n wins the engine room: Community Edition runs on a self-hosted server at no licence cost, and its code is open to read and change for internal use. Moxo wins the approval itself: its API refuses a step completion from an organisation key, a stalled step has named moves, and its documented deletion keeps the audit rows. Run together, n8n carries the volume and Moxo's flow meter counts only the exceptions. Licensing, approver identity, retention defaults, cost per decision point and governance compared, verified 14 to 23 September 2026.