Limits & Quotas
Every workflow operates within platform limits. Understanding these limits helps you design workflows that run reliably and avoid unexpected failures.
Execution limits
| Limit | Free | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Execution timeout | 60 seconds | 5 minutes | 15 minutes | 60 minutes |
| Max nodes per workflow | 25 | 50 | 100 | 500 |
| Max workflows | 5 | 25 | 100 | Unlimited |
| Active workflows | 3 | 15 | 50 | Unlimited |
| Executions per month | 500 | 5,000 | 50,000 | Custom |
| Concurrent executions | 2 | 5 | 20 | Custom |
Data limits
| Limit | Value |
|---|---|
| Webhook payload size | 5 MB max |
| HTTP Request response size | 10 MB max |
| File upload size | 25 MB per file |
| Variable data size | 1 MB per variable |
| Output data per node | 5 MB max |
| Total execution data | 50 MB across all nodes |
Rate limits
| Limit | Value |
|---|---|
| Webhook triggers | 100 requests/minute per webhook URL |
| HTTP Request node | 50 concurrent requests per workflow |
| Email sending | 100 emails/hour (Free), 1,000/hour (Starter), 10,000/hour (Pro) |
| API calls | Based on plan (see API Keys) |
Loop limits
| Limit | Value |
|---|---|
| For Each iterations | 1,000 max items per loop |
| Loop Until iterations | 100 max iterations |
| Repeat node | 50 max repetitions |
| Nested loops | 2 levels max (loop inside a loop) |
Credit limits
| Plan | Monthly credits |
|---|---|
| Free | 100 |
| Starter | 5,000 |
| Pro | 25,000 |
| Enterprise | Custom |
See Credits & Usage for what consumes credits.
Wait limits
| Limit | Value |
|---|---|
| Wait for Webhook timeout | 7 days max |
| HITL timeout | 30 days max |
| Delay max duration | 30 days |
| Concurrent waiting workflows | 10 (Free), 50 (Starter), 100 (Pro) |
What happens when limits are hit
| Limit reached | Behavior |
|---|---|
| Execution timeout | Workflow stops at the current node. Status: Failed. Error: "Execution timeout" |
| Max nodes | Cannot add more nodes in the builder. Existing workflows continue to run. |
| Payload too large | Trigger returns 413 error. Workflow does not start. |
| Rate limited | Trigger returns 429 error with retry-after header. |
| Credits exhausted | AI/scraping/vision nodes fail. Non-credit nodes continue. |
| Concurrent limit | New executions are queued (up to 1 hour). If still at capacity, they fail. |
| Loop limit | Loop stops at the iteration limit. Remaining items are skipped. |
Designing within limits
| Challenge | Solution |
|---|---|
| Execution timeout | Break long workflows into multiple workflows chained via webhooks |
| For Each 1000 limit | Process in batches: first 1000, then trigger another run for the next 1000 |
| Payload too large | Store large data in a database or file storage, pass a reference URL instead |
| Rate limits on external APIs | Add Delay nodes between requests (e.g., 1 second between each API call) |
| Credit budget | Filter data before expensive nodes to reduce the number of AI/enrichment calls |
Note
Limits are enforced at the workspace level. All workflows in your workspace share the same execution and concurrency quotas. If one workflow uses all concurrent slots, others will queue.
Tip
Check your current usage against limits in Monitor → Usage. Set up notifications in Settings → Notifications to alert you when you're approaching limits (80% of monthly executions, low credits, etc.).