Overview
Automations can query and take action on large amounts of data. To make sure they run in a timely fashion, there are a few limits to what automations can do.
| Item | Limits |
|---|---|
| Triggers | Every automation can only have one trigger |
| Steps | Every automation supports a maximum of 50 steps, including logic |
| Max runtime for an automation | An automation cannot run for more than 45 days total |
| Delays | A single delay step cannot exceed 30 days |
| Timeout for external automation steps | Calls to external applications, including APIs/webhooks, will time out after 60 seconds |
| Bulk operations | Bulk operations cannot iterate more than 1,000 times |
| Query Rippling data | You can retrieve a maximum of 50,000 records in one automation run using the Query Rippling data step. If a collection contains more than 50,000 records, the automation may fail |
| Emails | A maximum of 10,000 emails can be sent per company per day across all automations. An email message can have a maximum of 500 recipients. If you configure an automation to send to both personal and work email addresses, 2 emails will be sent each time it triggers, causing you to reach this limit sooner. For example, if 350 people are included as recipients, but the message is configured to send to both personal and work emails, 700 emails will be sent, causing the automation to fail. If you need to direct something to a large group of people, consider using an email group (i.e., “all@company.com”) |
| SMS | SMS is limited to 500 characters total. If the body text exceeds 500 characters, the message will fail to send. If the body text exceeds 160 characters, the message will be split up and sent as multiple messages |
| Slack messages | Group direct messages are limited to 8 recipients |
| Teams messages | Group direct messages are limited to 30 recipients |
| Make a payment | Automations can send payments to a maximum of 50 people at once. If an automation attempts to make payments to more than 50 people due to a single trigger event, it will fail, and no payments will be made. Individual payments are limited to $5,000. For example, if you set the payment amount in an automation to $5,000 and the automation triggers for 3 employees, each of those 3 employees will receive a $5,000 payment. Automations cannot add payments to pay runs that get auto-approved. If an automation attempts to add a payment to an auto-approved pay run, it will fail. Learn more in our article about making a payment with an automation. |
| RQL functions | When using RQL to define a variable, the following functions are not available: SELECT, REPORTSTO, ORG, WORKDAYS, ADDWORKDAYS, HIERARCHYPATH, PERCENTRANK |
Scheduled automations with filter conditions run once for each matching record, up to 5,000 records. The automation is executed in parallel for all matching records. If there are more than 5,000 matching records, or if no records match the condition, the automation will not run. For more information, see Triggers.