Technical Guide

n8n credential expired — why it happens, what to do, and how to stop finding out from your client

November 2026 · Ashim Doley · Okum

The most common failure in production n8n is not a code bug. It is a credential that stopped working — usually an OAuth token that expired while the workflow kept trying to use it. The workflow fails, the error message says something about authorisation, and if you run workflows for clients, the client finds out before you do.

This page covers why it happens, what the error messages actually mean, how to fix each case, and how to stop being the last person to know.

How OAuth credentials expire in n8n

OAuth uses two tokens:

n8n handles access token refresh automatically — you do not need to do anything for that. The problem is when the refresh token itself dies. Then n8n cannot get a new access token, and every API call fails with a 401 or invalid_grant.

When refresh tokens die

ServiceRefresh token lifespanCommon trap
Google (Testing mode)7 daysGoogle Cloud app is still in "Testing" — the #1 cause of weekly re-auth
Google (Published)6 months of inactivityA workflow that runs daily is fine; one that runs monthly may lose its token
Microsoft90 days (default)Password change invalidates all tokens immediately
SlackDoes not expireUser revoking the app in Slack settings
HubSpot6 monthsChanging OAuth app scopes invalidates existing tokens
The Google "Testing" trap: If your Google Cloud OAuth consent screen is still in "Testing" status, refresh tokens expire every 7 days. This is by far the most common cause of repeated credential expiry. Publishing the app to "Production" extends this to 6 months. You do not need Google to verify your app for internal/personal use — just move it out of testing.

What the error messages mean

n8n credential errors come in several shapes. They all mean roughly the same thing, but the fix depends on which one you see:

Error messageWhat it meansFix
invalid_grantRefresh token expired or revokedReconnect the credential from scratch
401 UnauthorizedAccess token invalid and refresh failedReconnect the credential
Unable to sign without access tokenn8n tried to sign the request but had no token at all — it failed before the API call was ever madeReconnect or delete and recreate the credential
Token has been expired or revokedGoogle explicitly says the token is deadReconnect + check Google Cloud testing status
credentials not foundThe credential was deleted or never finished setupCreate a new credential and select it in the node
The sneaky one: Unable to sign without access token has no HTTP status code. It happens before n8n sends the request, at the signing step. If you are matching on HTTP 401 to detect dead credentials, you will miss this entire class. It is one of the most common Google OAuth failures in real production data.

How to fix each case

Step 1: Reconnect the credential

  1. Go to Credentials in n8n
  2. Find the affected credential
  3. Click Reconnect (or "Sign in again")
  4. Complete the OAuth popup
  5. Run a test execution to confirm it works

Step 2: If reconnecting does not work

  1. Delete the credential entirely
  2. Create a new one from scratch
  3. Go through the full OAuth flow
  4. Select the new credential in every node that used the old one

Step 3: Prevent it from happening again

The real problem: finding out before the client

Fixing a credential takes 2 minutes. The damage is not the fix — it is the 3 days between the credential expiring and someone noticing. In those 3 days, the workflow keeps failing, the client's data stops updating, and the first person to notice is the client, not you.

The client doesn't experience three weeks of silent failure as three weeks. They experience the thirty seconds where they ask what happened and you don't have an answer.

An error workflow helps — but only for the failures that throw an error. Some credential failures are silent (the node continues after error), and an error workflow cannot tell you whose credential expired or which client is affected.

Whose fault is it? Not always what you think

This is the part that matters if you run workflows for clients. A dead credential is not always the client's fault, and it is not always yours:

SituationWhose sideWhat to do
OAuth token expired (was working, stopped)Not your bugRe-authorise in n8n, notify client if their action caused it
Credential was never finished (setup incomplete)Your setup issueOpen the node, complete the OAuth flow
Client changed their passwordClient's actionTell the client, re-authorise together
Client revoked the appClient's actionTell the client, re-authorise together
Google Cloud app still in "Testing"Your setupPublish the app, re-authorise

Getting this distinction right — quickly, without digging through logs — is the difference between "your OAuth token expired on the 4th, here is the trail" and "I am not sure yet." The first keeps the relationship. The second turns a technical failure into doubt about whether the agency is in control.

This is what Okum automates. It classifies every credential failure — expired, never connected, client revoked — and tells you whose side it is on, in the alert itself. You know what to do before you open n8n.

Try it free for 14 days → · No card required.