Agent skill · software engineering · n8n-io
n8n:node-add-oauth
Add OAuth2 credential support to an existing n8n node — creates the credential file, updates the node, adds tests, and keeps the CLI constant in sync. Use when the user says /node-add-oauth.
Why this skill is useful
Adds a complete automation script for integrating OAuth2 support into n8n nodes, including credential file creation and testing.
What it needs
Requires n8n installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
Overview Add OAuth2 (Authorization Code / 3LO) support to an existing n8n node. Works for any third-party service that supports standard OAuth2. Before starting, read comparable existing OAuth2 credential files and tests under packages/nodes-base/credentials/ to understand the conventions used in this codebase (e.g. DiscordOAuth2Api.credentials.ts, MicrosoftTeamsOAuth2Api.credentials.ts). --- Step 0 — Parse arguments Extract: NODENAME: the service name (e.g. GitHub, Notion). Try to infer from the argument; if ambiguous, ask the user. CUSTOMSCOPES: whether the credential should support user-defined scopes. If the argument does not make this clear, ask the user before proceeding: "Should users be able to customise the OAuth2 scopes for this credential, or should scopes be fixed?" --- Step 1 — Explore the node Read the following (adjust path conventions for the specific service): 1. Node directory: packages/nodes-base/nodes/{NODENAME}/ Find .node.ts (main node) and any Trigger.node.ts Find GenericFunctions.ts (may be named differently) Check if an auth / version subdirectory exists 2. Existing credentials: packages/nodes-base/credentials/ — look for existing {NODENAME}Api.credentials.ts files to understand the naming convention and any auth method already in use. 3. package.json at packages/nodes-base/package.json — find where existing credentials for this node are registered (grep for the node name). --- Step 2 — Research OAuth2 endpoints Look up the service's OAuth2 documentation: Authorization URL Access Token URL Required auth query parameters (e.g. prompt=consent, accesstype=offline) Default scopes needed for the node's existing operations Whether the API requires a cloudId / workspace ID lookup after the token exchange (Atlassian-style gateway APIs do; most services don't) If you can't determine the endpoints confidently, ask the user to provide them. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/node-add-oauth