Airtable Node not working

Questions
1

Describe the problem/error/question

Hello, starting today at 7 AM UTC, the Airtable node began returning timeout errors, but not for all requests. Which requests cause the error seems to be random. Is this a bug or an issue on the N8N or Airtable side?

What is the error message (if any)?

The connection timed out, consider setting the ‘Retry on Fail’ option in the node settings

Please share your workflow

All Airtable workflows

Share the output returned by the last node

Information on your n8n setup

  • **n8n version:**1.118.2
  • Database (default: SQLite): PostgreSQL 17.6 on x86_64-pc-linux-musl
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker - coolify
  • Operating system: linux
1 Like
2

Hi,
I’m experiencing exactly the same issue since this morning — random timeouts on all my Airtable nodes.

Here’s what I’ve tried so far:

  • Replaced Airtable nodes with HTTP Request nodes → same intermittent timeout errors

  • Regenerated my Airtable Personal Access Token and tested both Personal Access Token API and OAuth2 API connections

  • Updated n8n to the latest version

Interestingly, I’ve never had any timeout issue when making the same requests from Postman.

Here are my setup details:

core

  • n8nVersion: 1.119.1

  • platform: docker (self-hosted) - coolify

  • nodeJsVersion: 22.21.0

  • nodeEnv: production

  • database: PostgreSQL 17.6

  • executionMode: scaling (single-main)

  • concurrency: -1

  • license: enterprise (production)

Have you found where the issue comes from, or any possible workaround?

1 Like
3

I wanted to add that I don’t experience the timeout issue when running an n8n instance installed locally via npm on my Mac, using the same Airtable API key as the instance running on Coolify.

This seems to indicate that the problem is not with Airtable or the API key itself, but could be related to the Coolify/docker environment.

4

Hey same issue here. Self hosted n8n nginx and zero changes. Logged an airtable ticket also. Its broken my entire live publidhing flows. Maybe airtable made a change..will see what they say..

5

We tried using different API keys and HTTP Request nodes, but that didn’t help either. There’s nothing in the Docker logs that could help us resolve the issue.

6

Hey

My Airtable is working just fine again now with no changes by me. Im guessing it was an Airtable issue/change - they havent replied to the ticket but as no changes to my side and now it just works maybe they played with the api quotas…

Either way im reassessing airtable as its a massive single point of failure - all my production flows use airtable!! ..interested in any baserow experiences - it looks great just a lot of migration work…