Find your fit
Who it is for
It suits teams that repeat a process across clients, hires, incidents or approvals and want the same steps to be followed each time. The master workflow can be drafted privately, then shared with the organization when ready; each run keeps its own progress and captured information.
A team needing handoffs can assign tasks by role, collect responses with form fields and route review through approval tasks. Admin, Builder, User and Guest roles provide different participation levels; map those roles to the people who will build, supervise or simply complete work.
The work it supports
Core capabilities
A builder can start from a blank workflow, a premade template, an existing document or an AI-generated draft. Treat the draft as a process design: identify steps, required information, owner and review point before letting it become a shared operating procedure.
A workflow is the reusable master; a workflow run is one instance of it. For example, a team can use one onboarding procedure repeatedly while tracking each onboarding as its own run. The distinction matters when planning reporting and later changes to the master.
Role assignments can direct tasks to whoever fills a role in a particular run. This supports a handoff from the person starting the process to another team member, but the exact assignee and guest permissions should be checked with a sample run.
Form fields capture case-specific files, notes and other values. Conditional logic can reveal relevant instructions or tasks based on entered answers, letting one workflow handle a bounded variation without presenting every branch to every participant.
Approval tasks add a signoff step to a workflow and can be arranged as single or sequential reviews. Use them for decisions that genuinely need another person, and test who can submit, approve and continue a run.
Admins and Builders can export workflow-run records to CSV for spreadsheet analysis or recovery checks. The documented export includes task, form-field, assignee and status data; dates are in UTC. Test a representative export if this data must feed another system.
Understand the offer
Pricing and getting started
The current site offers Startup, Pro and Enterprise through contact-sales quotes rather than a public fixed price. It advertises a 14-day Pro trial without a credit card. Ask sales for the actual seat count, subscription total, billing period and post-trial offer.
Startup currently lists five users and ten guests. Its card also lists 5,000 Data Set records, a 5 MB per-file limit, ten automation apps and 100 automation actions per month. Check whether these fit a real recurring process before using the plan as a small-team default.
Pro lists custom user and guest counts, 10,000 Data Set records and a 100 MB per-file limit. Enterprise presents custom allowances for these dimensions. These are card descriptions; the sales quote should confirm the rights and limits that will actually be enabled.
Seat math needs care. The current help says Admins, Builders and Users are billable for organizations created on or after August 1, 2025, while earlier organizations count only Admins and Builders. Monthly and yearly billing are described, with a lower per-user rate on yearly subscriptions; obtain the applicable role and term rules in writing.
Look a little closer
Before you choose
Pilot one fictional workflow with a creator, an assignee and an approver. Start two separate runs, enter different form answers, exercise a conditional branch and confirm who sees or completes each task. That tests the actual handoff before introducing customer or employee data.
Check how revisions to a master procedure affect active runs before making a heavily used workflow the operational source of truth. The official help distinguishes the master from each run, so a buyer should verify change behavior with a safe sample rather than assuming every open case updates in place.
If records will be audited or moved elsewhere, export a few sample runs to CSV and inspect task, answer, assignee, status and UTC date fields. The documented CSV is about run data; confirm separately whether the workflow design, files and approval history meet your retention needs.
Separate the platform quote from trial eligibility and seat allocation. Startup has fixed published seat and usage numbers, Pro and Enterprise use custom allowances, and the billable-role rule changes with organization creation date. Confirm the exact plan and billing term before onboarding a full team.
11 distinct sources behind this profile. Research observed Oct 26, 2026. Features and offers can change.
View sources and research →
