Airtable Create Record Integration Fails Due to Rate Limit Issues | Clay

Airtable Create Record Integration Fails Due to Rate Limit Issues

Airtable's rate limit is not respected in the Create Record integration/enrichment. When trying to create around 100 records, a significant chuck of them fail with this error. I've not seen this when doing much larger operations with the "lookup record" enrichment, so I'd guess that the rate limit has not been applied to the Create Record endpoint (or the endpoint has a smaller rate limit than the other endpoint).

{"errors":[{"error":"RATE_LIMIT_REACHED","message":"Rate limit exceeded. Please try again later"}]}

7 comments

Channeled
APP
·
·
The issue occurs because Clay has a rate limit of processing up to 10 records per second, with a maximum burst capacity of 20 records per workspace. When trying to create 100 records at once, you're likely exceeding these limits. To resolve this issue, you can: 1. Process your records in smaller batches to stay within the rate limits 2. Start by testing with a small sample (around 10 rows) to verify the process works correctly before attempting larger batches If you have multiple webhook sources active in your workspace, you'll need to be especially mindful of these limits and may need to adjust your approach accordingly.
Sources: Import Data to Clay Using Webhooks Guide: Ways to save Clay credits | Documentation | Clay University
Mark J.
·
·
That didn't answer my question. That's the rate limit for data coming into Clay via the webhook integration. I'm talking about sending data out of Clay with the Airtable integration.
Mark J.
·
·
https://app.clay.com/workspaces/492338/workbooks/wb_RC6W9Viha4qA/tables/t_fqJMdE5FPQsj/views/gv_pwmSFNHdsU9i
Bo (.
·
·
Hey Mark
I've sent this feedback to our team. Typically, the integration should work properly, unless it's being used simultaneously in multiple places. But I still want to check with the team to be sure though.
Bo (.
·
·
Hey Mark,
I just heard back from our team, and it looks like our integration is properly set up. The errors you're seeing might be due to the API being used in multiple places simultaneously.
Could you flag it to us if this happens again? If possible, please leave the columns as they are so our team can investigate the issue further. Thank you.
Mark J.
·
·
Thanks for the update! Will do.
Channeled
APP
·
·