Airtable trigger in n8n failing "Created Time" field not found

Questions
1

I’m setting up an n8n workflow that should trigger whenever a new record is added to Airtable. I’ve configured the trigger to use the “Created Time” field that exists in my Airtable base.

However, when I run a test, n8n returns an error stating that the “Created Time” field does not exist, even though I can confirm it’s definitely there. I’m not sure if this is related to the field name formatting, API permissions, or something else like the URL configuration.

Has anyone encountered this before?

2

Hey @stonewall, while you wait for a response, here are some things that might help:

Suggested resources

Automatically matched to your question.

Docs:

Forum:

@blackqwar, @Parintele_Damaskin, @Olek - you’ve helped with similar issues before, can you take a look?

Automatically suggested by n8n’s community bot. It’s a pilot - please share feedback here.

3

Hey @stonewall Welcome to the community,
The airtable node does an exact key lookup for your trigger field inside the record’s fields object, and Airtable’s built-in creation timestamp isn’t in there. The API returns it as a top level createdTime on the record, outside fields, so pointing the trigger at it produces exactly this error even though you can see the time in Airtable.

Add a real column to the table with the field type Created time, then put that column’s name in Trigger Field. Match it character for character, since the lookup is case sensitive and Airtable names that type “Created time” with a lowercase t.

4

Hi @stonewall
The Fields and View ID options can strip the trigger field out of the response even when the column is correct. On a manual test the node drops its filter and asks Airtable for a single record with maxRecords set to 1, and Airtable returns only the fields those two options allow, so the lookup can come up empty on a column that is perfectly valid. Airtable also omits any field that is empty on whichever record it happens to return.
Clear Fields and View ID under Options and test again, or add the trigger field to the Fields list.
See this:

5

That error usually means n8n cannot resolve the field in the exact table selected, rather than the timestamp value being empty. I’d reset it in this order:

  1. In that same Airtable table, confirm the column’s field type is Created time, not a normal Date field or a formula merely named “Created Time.”

  2. In n8n, reselect the Base and Table, then choose the Trigger Field again from the picker. If you added the Airtable field after configuring the node, refresh/reopen the node so its schema is reloaded.

  3. If you pasted URLs or IDs, copy them from the exact table; a similarly named table in the same base is an easy mismatch.

  4. Confirm the Airtable credential/token can read that base and its records.

  5. Start the manual test first, then create a brand-new record. The Airtable Trigger polls and uses that field to decide what appeared since the previous check.

If it still fails, temporarily rename the column to something simple like CreatedAt, reselect it in n8n, and share a screenshot of only the Base/Table/Trigger Field settings plus your n8n version. Redact the token and base contents.

6

This worked thanks, note i also switched to ID rather than URl