[Bug?] Airtable API Connection Unauthorized After Few Minutes (Cloud Instance v1.89.2)

Questions
1

Hi n8n community,

We are facing a persistent issue with the Airtable API integration on our n8n Cloud instance.

Environment Details:

  • n8n Version: 1.89.2
  • Hosting: n8n.cloud
  • Service: Airtable Personal Access Token (not legacy API key)

Problem Description:

  • We have generated a valid Airtable Personal Access Token with all required scopes:
    • data.records:read
    • data.records:write
    • schema.bases:read
  • The token is correctly scoped and authorized to access the necessary base.
  • Upon setting the token in n8n, the connection initially works.
  • However, after a few minutes, the connection fails automatically with the error:
    • Couldn't connect with these settings – Unauthorized
  • Regenerating and replacing the token temporarily resolves the issue, but the same problem repeats after a short while.
  • This is interrupting our workflows heavily.

What we have tried:

  • Regenerated and re-applied the Airtable token multiple times.
  • Verified Airtable access permissions.
  • Confirmed the correct scopes are active.
  • Ensured the correct base is being targeted.
    API error
    API error1319×640 42.3 KB
2

Same here. The workflow and AirTable node were working as usual until they suddenly stopped working (timeout). I tried using the exact same login details with curl and it still worked. According to ChatGPT, AirTable may have changed the API so that the n8n AirTable node can no longer handle it?

3

I’m not entirely sure what the root cause is. The Airtable personal access token works fine on other platforms after granting access once, so the token itself seems to be valid. This issue seems to be happening only with n8n, and it’s affecting all of our projects there.

4

I have just tried to reproduce this and it appears to be working for me. How long is it taking to show the failure message?

At any point did you change the credential to use an expression then click save or has that field remained masked?

5

Thanks for checking and testing this.

To clarify:

  • The failure message doesn’t appear at a fixed interval. Sometimes it happens within a few minutes, sometimes after a few hours. There’s no consistent pattern.
  • We did not change the token field to use an expression at any point. The field remained masked throughout and was saved as-is.
  • This issue is affecting all 4 developers on our team, each working on separate workflows within the same n8n Cloud workspace.
  • The only workaround we’ve found is to regenerate and re-add a new Airtable token each time the connection fails. But this is disruptive to our workflow development and testing.

Let us know if there’s anything else we can try or check on our end.

6

I have it running on a schedule now on a cloud instance and a self hosted instance as the node is in theory the same. Next time it fails can you try running the workflow below using the same credential as the node this uses the same endpoint as the credential test and will hopefully give us more information on why it is failing.

7

Thank you. Jon. I have been re authorising api token and so far it is still working. I’ll keep an eye on the issue and will update you back.