There is no hard cap on the number of automations you can run, the number of steps in a single workflow, or the delay between steps. The only real boundary is your credit balance — sending email or SMS costs credits, but triggering and internal actions cost nothing. Two safety rules apply per contact: a same contact can only fire the same workflow once every 24 hours, plus a 60-second cooldown between consecutive fires.
What is actually capped
| Limit | Value |
|---|---|
| Active automations per account | No hard limit |
| Steps per workflow | No explicit cap |
| Delay between steps | No cap (days, hours, minutes) |
| Same contact × same workflow per day | Once every 24 hours |
| Cooldown between consecutive fires (same contact, same workflow) | 60 seconds |
Why a once-per-day re-fire limit exists
An automation can be wired so that one of its actions also satisfies its own trigger condition — for instance, a Tag-added workflow that adds another tag at the end. Without a guardrail, this would loop forever. The once-per-day rule means the same contact cannot re-enter the same workflow within 24 hours of their previous run. The skip is silent: no error log, no credit debited.
Why the 60-second cooldown exists
The cooldown is the second line of defence against fast loops — for example, an integration that quickly applies and removes a tag. If the same workflow tries to fire for the same contact within 60 seconds of the previous fire, the second attempt is skipped silently. This protects your delivery reputation from accidental rapid-fire sends without you having to police it manually.
What does cost something
Credits are spent only on the message-sending actions: one credit per email, one credit per SMS. Triggering an automation is free, even at high frequency, and internal actions (tag, list, internal alert) are free too. To estimate monthly cost, multiply the average number of sends per month by your email credit rate (or SMS rate) and ignore the rest.
Build without worrying about the limits
Browse the automation triggers and actions, or set up automatic credit recharge so your sends never wait on balance.