Airtable trigger FORBIDDEN, Creds are 100% ok

Questions
,
1

Hello, I have problems with airtable trigger. I use the same (working) credentials that works perfectly in a different workflow (not as trigger). But in my new workflow, I get this error permanently

Forbidden - perhaps check your credentials?

403

Full message

{ "error": { "type": "INVALID_PERMISSIONS_OR_MODEL_NOT_FOUND", "message": "Invalid permissions, or the requested model was not found. Check that both your user and your token have the required permissions, and that the model names and/or ids are correct." } }

Invalid permissions, or the requested model was not found. Check that both your user and your token have the required permissions, and that the model names and/or ids are correct.

How can the same credentials work in a different workflow?

I double checked Base, Table and View IDs all correct :frowning:

anybody know a work around?

Community Version n8n Version 1.56.2
Installed on Digital Ocean Docker.

1 Like
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

Hi @a.prior,

Welcome to the community! :cactus:

Could you try creating another credential with the same settings as the one you’re trying to use now and see what is the output of that? That might give us a clue wether this is on n8n or on the settings.

Let us know how you get on! :slight_smile:

4

having the exact same issue, I’v tried 3 different tokens, I’m self hosted in docker. I know it connects to airtable cause it is green, then it can see the DB, and then it can see the tables that I select. So all good there. Yet when I test it, it gives me that same message. Pulling my hair out

5

The error message is coming back from Airtable and they believe the credential doesn’t have access to the data you are trying to use.

Is the token restricted to a base or table maybe? As this isn’t an error we generate it is hard to know what Airtable actually means.

6

Found the issue, and maybe need to fix this in the software. The N8N installation allowed me to “see” my table, but, the PIN from the initial webhook from the initial builder was to his IP address. So I was trying to connect to his DB instead of mine, so of course it didn’t have the creds. You may say “well of course it didn’t work”, but I think if you take a step back, you can see that this can cause confusion especiallly if everything is “green”, yet not working. just my 2 cents… either way that was my issue, thanks for your responce

1 Like
7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.