Clay Rate Limits with Airtable Integration: Key Considerations

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 back to Airtable the same Airtable Rec_ID? Thank you!