Workflow billing
A journey's cost depends on how many runs start, how many steps they execute and where AI is used. Workflow execution spends workspace credits; email also draws on the shared sending allowance. Plan these components together before scaling a journey.
What a step costs
Every step maxclicks runs charges an operation fee. Steps that call an AI model also bill the tokens that model used.
| Step | Charge |
|---|---|
| Find Records, Set Value, Query, For Each, the action steps, and a compiled If/Else, Switch or Delay | Operation fee. |
| AI | Operation fee plus AI tokens. |
| An If/Else, Switch or Delay left uncompiled | Operation fee plus AI tokens: maxinja works it out on every run. Compiling moves interpretation to authoring rather than repeating it during every run. |
| Send Email | Step operation fee, plus email allowance for the message and model usage when the content is AI-personalized. Overage applies beyond the included email allowance. |
Every charge is tagged with the workflow, the version it ran, the run, and the step. None of that reaches the screen: Billing, then Usage, reports spend by period, by category (Workflows is one) and by member, and never breaks it down per workflow, per run or per step.
The message uses the shared email allowance: Free is capped at 100 emails per month; Premium includes 1,000,000 per month before overage. The workflow step still has its execution fee, and AI personalization adds model usage. Included email delivery does not add a per-recipient send fee.
Running out of credits
When step execution cannot obtain credits, it waits and checks again. Adding credits can let that waiting work continue; creating a replacement run risks doing the work twice. Premium also allows a limited negative-credit buffer, so a displayed balance at zero is not a precise stop switch.
Credit waits are different from terminal failures such as invalid step data, an unusable sender domain or exhausted email allowance. Topping up does not repair a run already marked Failed. Inspect the run reason first.
Step charges are recorded for each executed step occurrence. Safe infrastructure retries reuse that charge and recorded effects rather than charging the same occurrence again. AI generation, correction and email rendering still have their own applicable usage. A new run or intentional new generation is new work.
Concurrent run cap
Each space has a ceiling on runs active at once: 1000 plus 20 per object record. The cap scales with your data, so larger spaces run more in parallel.
A step set to process each record separately creates child runs; For Each creates one per item. Work beyond the active-execution capacity waits for a turn. Durable sleeping delays do not occupy an active execution slot for their whole wait. The cap controls simultaneous execution, not the lifetime total of journeys you may start.
The cap limits pressure on the workspace, but it is not a campaign budget. An indirect loop can still generate continuing work: workflow A fires an event for B, and B updates a record that triggers A again. Design conditions that stop that cycle and review fan-out before publishing.
Managing usage
Admins review credit usage in the space's billing settings. On Premium they set the auto-recharge amount and threshold, and top up the wallet with a manual charge ($10 to $10,000).
Related
- Workflows: steps, versioning, and the trigger API.
- Workflow runs: what each run did.