Authenticate a user in a workflow with OpenID Connect
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 12 nodes and runs when an HTTP GET request hits its webhook URL. It uses only n8n's built-in nodes.
How it runs
Trigger: When an HTTP GET request hits its webhook URL.
- Set variables : auth, token, userinfo, client id, scope (Edit Fields (Set)): sets or maps fields
- Code: runs custom JavaScript code
- If: checks a condition and branches into true / false
- get access_token from /token endpoint with code (HTTP Request): calls an HTTP API (POST)
- If: checks a condition and branches into true / false
- user info (HTTP Request): calls an HTTP API
- login form (HTML): parses or builds HTML
- If: checks a condition and branches into true / false
- send back login page (Respond to Webhook): sends the response back to the webhook caller
- Welcome page (HTML): parses or builds HTML
…plus 1 more step. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - Respond to Webhook
n8n-nodes-base.respondToWebhook - If
n8n-nodes-base.if - HTML
n8n-nodes-base.html - Edit Fields (Set)
n8n-nodes-base.set
From the author
Intro This workflow needs a user to authenticate by using an openid connect provider in order to call the webhook. If the user is not authenticated, it starts a login process by using an Authorization Code with PKCE…