Compared with Zapier, n8n, Make and Power Automate.
Compare how these products draft workflows, assign work and handle approvals. In Standard Procedure, you assign steps to agents and teammates, and choose where work needs review. A job can involve:
- An agent
- A teammate
- A client who sends the request
- You, at the steps you mark
When you edit or correct an agent’s work, the procedure learns automatically and uses the lesson on future jobs. Your data, procedures and the knowledge built from those corrections remain yours.
Standard Procedure is in early access, with setup handled by our team. The other products publish prices and offer self-service signup. Each comparison includes their documentation and plan details.
Side by side
| Standard Procedure | Zapier | n8n | Make | Power Automate | |
|---|---|---|---|---|---|
| How a process gets built | Describe the job or upload a checklist. An agent drafts the procedure for review. You assign steps to people and agents and choose where work needs approval. | A visual editor. Copilot, in open beta, outlines a Zap from a description and helps configure each step. | A visual canvas. The AI Workflow Builder creates and refines workflows from a description. | A visual scenario builder. Maia, in public beta on paid plans, creates, changes and debugs scenarios from a prompt. | A flow designer. Copilot creates a cloud flow from a description and edits it on request. |
| Improving future runs | Edits and corrections automatically become lessons for future jobs. Agents apply what your team has taught the procedure, with no separate training task. | Ask Copilot to edit the Zap’s steps, then publish the revised workflow. | Ask AI Workflow Builder to revise the workflow. Memory nodes can retain an AI agent’s conversation history when configured. | Maia remembers builder preferences automatically. You ask it to change a scenario; its memory excludes scenario-specific details. | Ask Copilot to change actions in the flow, or edit them in the designer and save the changes. |
| Where work waits for a person | At the review steps you choose. Connection calls also require approval by default; only a person can change that setting. | A Request Approval step from Human in the Loop pauses the Zap for reviewers. Paid plans only. | “Send and Wait for Response” on Slack or Microsoft Teams, and human review before an AI agent uses a tool you’ve flagged. | Add a review step with an approval app from Make’s catalog, such as HITL. | Approvals answered from Outlook, Teams or the action center, by users in your tenant, including accepted guests. |
| Connecting other systems | An agent builds connections to the systems your team uses from API docs. Each call starts switched off for you to review. Email, files, calendars, chat and payment tools are also built in. | More than 9,000 apps. | Hundreds of built-in nodes, community nodes, and an HTTP Request node for any REST API. | 3,000+ apps on every plan. | Microsoft’s connector catalog: standard connectors, premium connectors on paid plans, and custom connectors you build. |
| Pricing | Not published yet. We’re setting up the first businesses one at a time. | Per task. Free for 100 tasks a month; Professional from $19.99 a month, billed annually. | Per execution, one run of a whole workflow. Cloud Starter from €20 a month, billed annually. The self-hosted Community edition is free. | Credits, one per module action. Free up to 1,000 credits a month; Core from $9 a month. | Premium is $15 per user a month, paid yearly; Process is $150 per bot a month. Office 365 licenses include standard connectors. |
Facts about the other four come from their own pricing pages and documentation, checked . Each comparison links its sources.
Read a product comparison
- Standard Procedure vs Zapier → More than 9,000 apps, billed per task. Consider Zapier when its catalog covers the apps you need and you want task-based pricing.
- Standard Procedure vs n8n → Self-host it, or use n8n Cloud. Billed per workflow run. Consider n8n if you want to host workflows on your own servers, or use its Cloud service.
- Standard Procedure vs Make → 3,000+ apps on a visual canvas, billed in credits. Consider Make if you want to build scenarios on a visual canvas with credit-based pricing.
- Standard Procedure vs Power Automate → Microsoft cloud and desktop flows, with approvals in Outlook and Teams. Consider Power Automate for Microsoft 365 approvals or desktop application automation.