Airtable connection not working

Describe the issue/error/question

Yesterday, all workflows with Airtable nodes stopped working. The problem error is:
ERROR: UNKNOWN ERROR - check the detailed error for more information Autentification required.

See the whole response below.

Be sure I check the API key; it works in other contexts.

Thanks for the help.
Honza

What is the error message (if any)?

{"context":{},"name":"NodeApiError","cause":{"message":"401 - {\"error\":{\"type\":\"AUTHENTICATION_REQUIRED\",\"message\":\"Authentication required\"}}","name":"Error","stack":"Error: Request failed with status code 401\n    at createError (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/usr/local/lib/node_modules/n8n/node_modules/axios/lib/adapters/http.js:269:11)\n    at IncomingMessage.emit (node:events:539:35)\n    at IncomingMessage.emit (node:domain:475:12)\n    at endReadableNT (node:internal/streams/readable:1345:12)\n    at processTicksAndRejections (node:internal/process/task_queues:83:21)"},"timestamp":1657995815437,"message":"Authorization failed - please check your credentials","node":{"parameters":{"operation":"list","application":"appd4tPmeInAiBI2w","table":"Winners-Loosers","returnAll":true,"downloadAttachments":false,"additionalOptions":{"fields":["product_id","record_id"]}},"name":"Airtable1","type":"n8n-nodes-base.airtable","typeVersion":1,"position":[-180,560],"alwaysOutputData":true,"credentials":{"airtableApi":{"id":"2","name":"[email protected]"}}},"httpCode":"401","description":"Authentication required"}

Information on your n8n setup

  • n8n version: 0.186.0
  • Database you’re using (default: SQLite): default
  • Running n8n with the execution process [own(default), main]: default
  • Running n8n via [Docker, npm, n8n.cloud, desktop app]: docker

Please upgrade to the latest version 0.186.1

1 Like

Ok, will let you know – thanks!

You are welcome. That version specifically contains a fix for that issue so should hopefully also work for you (unless there is a another currently to us unknow bug).

1 Like

I can confirm it works again. Thanks for the quick help! :raised_hands:

1 Like

Great to hear! Have fun!