Search
English
Contents
  1. n8n Tutorial
Getting started
  1. What Is n8n
  2. Install n8n
  3. Interface Guide
  4. First workflow
  5. Data structure and items
Core concepts
  1. Expressions
  2. Credential management
  3. Common core nodes
  4. Webhook
  5. Code node
  6. Error handling
AI Automation
  1. AI Agent Basics
  2. Connect a Local Ollama Model
  3. RAG knowledge base Q&A
Real-world examples
  1. Google Sheets automation
  2. Telegram AI bot
Deployment and operations
  1. Self-hosting
  2. Backup and updates
  3. FAQ and troubleshooting

n8n Credentials Tutorial: Set Up API Keys, OAuth, and Google Authorization

When n8n connects to external services, the accounts, passwords, API keys, and OAuth authorizations it needs are stored in credentials. Credentials are stored separately from workflows:

  • You can reuse the same credentials across multiple workflows.
  • Exporting or sharing a workflow does not include credential contents.
  • Credentials are encrypted when stored in the database.

Add credentials

There are two ways:

  1. In a node, select Create new credential under Credential to connect with.
  2. On the home page, go to the Credentials tab → Add Credential.
Choose a service when adding credentials
Credentials → Create credential, then search for the service you want to connect

The fields you need to fill in vary by service. Forms usually include a link near the top to the official documentation.

Credential types

TypeDescriptionExamples
API Key / TokenGenerate a key in the service's dashboard and paste it into n8nOpenAI, Notion, Telegram Bot
Username and passwordEnter them directlySMTP, database, FTP
OAuth2Click a button to go to the service, sign in, and authorize accessGoogle, Microsoft, Slack

Example: Telegram Bot

  1. Search for @BotFather in Telegram, send /newbot, and follow the instructions to name your bot.
  2. BotFather gives you a Bot Token, such as 123456789:AAH....
  3. Add a Telegram API credential in n8n, paste the token, and save it.
Telegram API credential settings
Telegram API credential: paste the Access Token from BotFather, then click Save

For a detailed bot example, see Telegram bot.

Example: Google authorization for self-hosted n8n

With n8n Cloud, you can sign in to Google with one click. For a self-hosted setup, first create your own OAuth client in Google Cloud:

1. Create a Google Cloud project

  1. Go to Google Cloud Console and create a new project.
  2. Under “APIs & Services → Library,” enable the APIs you need, such as Google Sheets API, Gmail API, and Google Drive API.
  1. Go to “APIs & Services → OAuth consent screen” and select External for the user type.
  2. Enter an app name and contact email.
  3. Add your own Google account under Test users.

3. Create an OAuth client ID

  1. Go to “APIs & Services → Credentials → Create Credentials → OAuth client ID.”

  2. Select Web application for the application type.

  3. Paste the OAuth Redirect URL shown on the n8n credential screen into Authorized redirect URIs, for example:

    https://n8n.example.com/rest/oauth2-credential/callback

  4. After creating it, you’ll get a Client ID and Client Secret.

4. Finish authorization in n8n

  1. Add a Google Sheets OAuth2 API credential (or one for Gmail or Google Drive).
  2. Paste in the Client ID and Client Secret.
  3. Click Sign in with Google, sign in, and grant access.

The redirect URI must match exactly. n8n generates this URL using environment variables such as N8N_HOST, N8N_PROTOCOL, and the Webhook URL. If it shows http://localhost:5678, your deployment settings are not complete yet. See Self-hosting.

While the app is in “Testing” status, authorization expires sooner, so you may need to authorize again periodically. For long-term use, consider publishing the app to production (Google review may be required).

Use credentials in the HTTP Request node

When you call an API that does not have a dedicated node, select an option under Authentication in the HTTP Request node:

  • Predefined Credential Type: Use credentials for services n8n supports (such as Notion). You can call an API with the same credentials even if n8n’s Notion node does not support that API.
  • Generic Credential Type:
    • Header Auth: For example, name Authorization, value Bearer sk-xxx
    • Query Auth: Put the key in a URL parameter
    • Basic Auth: Username and password
    • OAuth2: Configure the OAuth endpoints yourself

Do not put API keys directly in the URL or Header fields, or they will be exposed when you export or share the workflow.

Credential encryption key

Credentials are encrypted with an encryption key. By default, the key is stored in the n8n data directory (/home/node/.n8n/config), or you can specify one with the N8N_ENCRYPTION_KEY environment variable.

  • When moving or restoring n8n, you must use the same encryption key, or none of the credentials can be decrypted.
  • Multiple n8n instances (for example, workers in queue mode) must use the same key.

See Backup and updates for backup instructions.

Sharing and permissions

By default, only the person who created a credential can use it. In the credential’s Sharing settings, you can share it with other users or projects (available features depend on your plan). People you share it with can use it in workflows, but cannot see its contents.

Updated October 12, 2026