The way I found resolved the issue is to completely delete the test record with the data in the Airtable table and add a completely new record in the table. It’s strange, it looks like zap is cashing the airtable configuration or something and it doesn’t replace with fresh Artable data immediately.Īnd that happens even if I select the new set of data in the trigger step. That wouldn’t be such an issue, I can go and fill in some data.īUT the issue is even after adding that information into Airtable (and refreshing zap or even reloading it), the newly added fields are still not showing up in the zap action step and it can take sometime or maybe an hour or so for them to show up.

I would rather prefer if it would show the fields whether it has some test data or not. If I am going through the process of setting up the zap and the Airtable table doesn’t have any appropriate data in it (…it usually happens if I miss to add some data in the table or it’s not in a view it should be…) then Zapier will not show the Airtable fields as existing (in the action step). One thing I find is an issue with Zapier is how it fails to refresh the test data while I am creating the zap workflow.

Google drive airtable zapier