Airtable "Created Time" returns -2h offset in n8n self-hosted (Berlin timezone)

Questions
1

Hi everyone,

I’m running a self-hosted instance of n8n (via Docker) and running into a timezone issue when pulling data from Airtable.

I have a base in Airtable that includes a “Created Time” field. When I use the Airtable node in n8n to search for records, the “Created Time” value is returned with a 2-hour delay (e.g. record shows 10:00 in Airtable, but n8n sees 08:00).

I’m in the Europe/Berlin timezone (UTC+2 currently). Here’s what I’ve configured so far:

Docker environment variables:

TZ=Europe/Berlin  
GENERIC_TIMEZONE=Europe/Berlin  
N8N_TIMEZONE_OFFSET=120

Workflow settings in n8n:
Timezone set to Europe/Berlin

When I test the same Airtable base using Make.com or other tools, the created time is correct (no offset).

Any idea what’s causing this discrepancy or how I can fix it in n8n?

Thanks in advance!

2

Maybe I’m stupid but try setting this to 0