Understanding Clay Rate Limits with Airtable Integration

Hi Everyone - I am using Clay with the Airtable integration (not Web Hook). A new record in Airtable triggers a Clay run. Are there Clay rate limits in place to prevent the action of a row completion from returning the updated content to Airtable with the same Airtable Rec_ID? The process flow also includes n8n, outside of the Clay/Airtable integration. Thank you!

2 comments

Channeled
APP
·
·
We don't have specific rate limits for the Airtable integration that would prevent updated content from being returned to Airtable with the same Rec_ID. However, we do have general rate limits for webhooks, which process up to 10 records per second with a maximum burst capacity of 20 records per workspace. For API integrations, you can define custom rate limits to control how many requests are sent within a given time frame. This helps prevent exceeding API rate limits of external services like Airtable. If you're experiencing issues with data updates or rate limiting, it might be helpful to review your integration setup. If you need further assistance, please request to talk to a person for more detailed support.
Sources: Import Data to Clay Using Webhooks HTTP API with JWT authentication | Documentation | Clay University
Channeled
APP
·
·