Airtable – New or Updated Record trigger not firing.
Status: Open · Asked by CenterSquareSoftwareLLC on · 0 views
Hello Pabbly Support Team,
I’m facing an issue with the Airtable – New or Updated Record trigger not firing.
I currently have two workflows using this same trigger, and both of them were working correctly before, but they are not triggering anymore now.
Here’s what I’ve already verified:
- The Airtable connection is active and connected
- Base and table are correctly selected
- I have created the ModifiedOn formula field exactly as instructed
LAST_MODIFIED_TIME() - I refreshed fields after creating the ModifiedOn field
- I updated existing records and also created new records
- I clicked Save & Send Test Request, but the response still shows 0
- No trigger event is detected even after confirmed record changes
This setup was previously working fine, so it seems like either:
- The trigger is not detecting updates correctly, or
- There may be an issue on the Airtable trigger side for my account
Could you please check:
- Whether there is any issue with Airtable triggers on free accounts
- If there are recent changes affecting the “New or Updated Record” trigger
- If my workflows are properly registered on your end
I’ve attached screenshots for reference.
Looking forward to your support.
Thank you!
Hello @CenterSquareSoftwareLLC,
Thank you for sharing the detailed information.
Upon checking your account
1. We can confirm that the Airtable – New or Updated Record trigger is working fine.
2. There are no recent changes or issues from our end affecting this trigger.
3. Your workflows are also properly registered and configured correctly in the system.
Could you please confirm if you have modified or created any other record in Airtable after the latest timestamp shown in the attached image.

Once you confirm this, we will be able to guide you further accordingly.
No, modifications or other created records after the timestamp shown above.
Hi @CenterSquareSoftwareLLC,
Thanks for the confirmation.
That explains why the workflow did not trigger — since there were no new records created or modified after the latest timestamp, the trigger did not detect any updates to capture.