Workflow Trigger Limits
Workflow Trigger Limits
Velaro caps the number of workflow triggers your account can fire each calendar
month. This protects your billing from runaway loops and prevents a single
misconfigured automation from racking up unexpected costs.
What counts as a trigger?
Every time a workflow starts — for any reason — it counts as one trigger. This
includes:
- A visitor message that matches a workflow trigger condition
- A Power Automate, Zapier, or Make flow calling the workflow API
- An AI bot deciding to hand off to a workflow
- A scheduled or recurring trigger
- Any custom webhook that starts a workflow
One trigger fire = one count, regardless of how many nodes the workflow runs.
Where to find your current usage
Admin → Billing & Usage → look for the Workflow Triggers This Month tile.
You'll see your current count, your monthly cap, and a progress bar.
Default caps per plan
| Plan | Workflow triggers / month |
|---|---|
| Starter | 5,000 |
| Growth | 25,000 |
| Professional / Pro | 50,000 – 100,000 |
| Scale / Enterprise | 500,000 |
| Custom / Internal | Unlimited |
Existing accounts created before this feature shipped have the cap set to
Unlimited until their plan is renewed or upgraded.
What happens when you hit the cap?
Once you hit the cap, new workflow triggers within that calendar month are
silently dropped (the workflow does not run). The trigger event is logged to
your Integration Activity Log (Settings → Integrations → Activity) with a
warning showing the current count and cap.
Counts reset on the 1st of each month (UTC).
How to raise your cap
- Self-serve: upgrade to a higher plan from Billing → Plan.
- Custom limit: contact support — we can set a custom cap on your
subscription without changing your plan.
Best practices
- Avoid recursive triggers: don't have a workflow whose final action triggers
the same workflow again. Use a guard condition.
- For high-volume external automation (Power Automate / Zapier / Make), use a
debounced trigger — fire the Velaro workflow once per batch, not once per
source event.
- If a Zapier/Make workflow fires unexpectedly often, check that source's
filter conditions before raising your cap.
Related
- Workflow Runs (separate metric, also capped per month)
- Active Workflows (how many published workflows you can have)
Was this article helpful?