Airtable Trigger in n8n Not Firing Despite Correct Setup

Questions
1

Hi team,

I’m experiencing an issue with the Airtable Trigger node in n8n, which is not firing as expected, even though all configuration seems correct.

Here’s what I’ve already checked:

  1. :white_check_mark: The Base ID and Table ID are correctly filled and verified.
  2. :white_check_mark: The Trigger Field (last_modified_status) exists in Airtable and is of type “Last modified time”.
  3. :white_check_mark: The Personal Access Token used has access to the base and table.
  4. :white_check_mark: I’ve tested updating records in Airtable (including creating new ones) to trigger the field, but no data is returned in n8n.
  5. :white_check_mark: I’ve also used the Fetch Test Event button – still no result.
  6. :white_check_mark: I confirmed that the field is monitoring updates to the correct data columns.
  7. :white_check_mark: I’m currently using a trial Airtable account – could this be affecting trigger functionality?
  8. :white_check_mark: I confirmed that other Airtable nodes (e.g., “Search”) work fine with the same credentials.

I’m polling every minute and expecting the trigger to return newly updated records, but nothing comes through.

Could you please advise if there are any known limitations (especially on free/trial plans) or hidden configuration requirements that might be affecting the trigger?

Thank you!

Best regards,

Honza

image
image801×797 32.3 KB

2

I was a heavy and advanced AirTable user myself, but now am spending most time on n8n and generally don’t do heavy lifting on AirTable anymore. While waiting for someone who might be more specialized in your use case to reply, I would just make a comment that simple Read and Writes to AirTable are very robust for me so far.

I don’t think a trial AirTable account would cause any issues, but I suspect there could be an implementation issue, if you are trying to watch a computed/built-in field like Last Modified Time.

I might decide to immediately invest some time in testing if the Airtable Trigger works for a standard Number or String field. Based on the result of that, we can easily know how to work around if a solution is immediately necessary. Either build a workaround using Airtable Trigger to watch simple fields, or to shift more work into n8n to build a polling loop using simple Read/Write nodes which might be considered more robust.

1 Like
3

I sorted out. Problem is it was behaving unexpectedly in testing mode.

I switched to production waited couple of minutes and it started working fine.

1 Like