n8n-credentials-and-security

Configure n8n workflows to store authentication secrets in credential fields.

421|46|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/n8n-io/skills --skill n8n-credentials-and-security
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-credentials-and-security
Source: https://github.com/n8n-io/skills/tree/main/skills/n8n-credentials-and-security
Command: npx skills add https://github.com/n8n-io/skills --skill n8n-credentials-and-security

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents credentials and tokens from being accidentally exposed in workflow fields, SDK code, exports, screenshots, or chat history by guiding the correct way to use n8n’s credential system for all auth-related needs.

Core Features & Use Cases

  • Credential-first security rules: keeps API keys, bearer tokens, OAuth secrets, passwords, and authorization headers out of plain text fields and expressions.
  • Correct credential selection and validation: explains how n8n auto-assigns the most recently edited credential of a given type and why you must verify each node’s dropdown selection.
  • Auth decision guidance: routes users to the right credential type based on service auth shape (native credentials, OAuth2, bearer/basic/header auth, or httpCustomAuth for multi-header/header+query patterns).
  • References for implementation details: provides supporting docs for the credential storage model, custom auth credential design, and HTTP Request auth wiring.

Quick Start

Tell the AI to configure your workflow to use the proper n8n credential type for the auth scheme you’re implementing, and then open every node that references a credential to confirm the correct one is selected in the dropdown.

Frequently Asked Questions about n8n-credentials-and-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I securely store API keys and bearer tokens in n8n workflows?

To securely store bearer tokens and API keys in n8n, use the built-in credential system instead of pasting secret values into plain-text workflow fields or expressions. This prevents accidental exposure in exports, screenshots, and chat history.

Which n8n credential type should I use for OAuth2 versus bearer token authentication?

For OAuth2 authentication in n8n, use the oAuth2Api credential type, while bearer tokens require the httpBearerAuth type. The auth decision depends on the external service's specific authentication scheme shape.

Why does n8n auto-assign the wrong credential to my HTTP Request node?

n8n auto-assigns the most recently edited credential of a given type to an HTTP Request node. You must manually open the node and verify the correct credential is selected in the dropdown to prevent authentication mismatches.

Can I use a custom auth credential for multi-header and query parameter authentication in n8n?

Yes, you can use the httpCustomAuth credential type in n8n for multi-header or header-plus-query authentication schemes. This handles complex external service auth patterns that standard bearer or basic auth cannot cover.

What happens if I put authentication secrets directly into n8n expressions or SDK code?

Placing authentication secrets directly into n8n expressions or SDK code literals exposes them in workflow fields, exports, and chat history. The credential system prevents this by securely managing OAuth, bearer, and basic auth values.

Does n8n support native credentials for external services or do I need HTTP Request auth?

n8n supports both native credentials for external services and HTTP Request auth wiring for custom APIs. Choose native credentials when available, otherwise route HTTP Request nodes through appropriate auth types like httpHeaderAuth.