Hello, community,
I am experiencing a very specific issue with the Airtable Trigger node and have been unable to find a solution.
The Issue: I am attempting to use the Airtable Trigger to start a flow when a record is updated.
I created a field in Airtable called n8n-Trigger Timestamp of type Last Modified Time.
I configured that field to watch only my Status field.
In the Airtable Trigger node in n8n, I use n8n-Trigger Timestamp in the Trigger Field.
The node fails with the error: The Field “n8n-Trigger Timestamp” does not exist.
What I have already verified (the important part):
The field name is 100% correct (copied and pasted).
The Base and Table URLs are 100% correct.
My Personal Access Token (PAT) has the correct permissions (data.records:read, schema.bases:read) and is assigned to this base.
The smoking gun: To test my configuration, I made a change:
In the same Airtable Trigger node, I changed the Trigger Field to point to a Created Time field that I also have in that table.
The node worked perfectly.
This proves that my credentials, permissions, and Base/Table URLs are all correct. The error seems to be specifically in how the Airtable Trigger node handles Last Modified Time fields.
Is this a known bug or an undocumented API limitation? Has anyone managed to use a Last Modified Time field with this node?
Thanks in advance!
This is a known issue with the Airtable Trigger node in n8n. Based on the [GitHub issues](Airtable trigger · Issue #15892 · n8n-io/n8n · GitHub), several users have reported the same “Field does not exist” error specifically with “Last Modified Time” fields, even when the field name and configuration are correct.
The issue appears to be a bug in how the Airtable Trigger node handles Last Modified Time fields through the API. As a workaround, you can:
• Use a different field type for triggering (like a regular date field that you update manually)
• Consider using Airtable’s native [webhook automations](When record updated Trigger | Airtable Support) to trigger your n8n workflow via HTTP webhook
• Monitor the [GitHub issue](Airtable trigger · Issue #15892 · n8n-io/n8n · GitHub) for updates on a fix
The fact that Created Time fields work confirms this is specifically related to Last Modified Time field handling in the trigger node.