Automatic Google Cloud Run auth with JWT token management (sub-workflow)
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 10 nodes and runs when another workflow calls it. Along the way it connects JWT.
How it runs
Trigger: When another workflow calls it.
- Combine Context (Merge): merges the data from its input branches
- Vars (Edit Fields (Set)): sets or maps fields
- If: checks a condition and branches into true / false
- Decode JWT (JWT): decode
- Sign New JWT (JWT): uses JWT
- If: checks a condition and branches into true / false
- Bearer YOUR_TOKEN_HERE Request (HTTP Request): calls an HTTP API (POST)
- Raise Id (Edit Fields (Set)): sets 1 field: id_token
- Return Values (Edit Fields (Set)): sets 3 fields: id_token, service_url, service_path
Services it uses
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 (6)
- If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Merge
n8n-nodes-base.merge - JWT
n8n-nodes-base.jwt - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - HTTP Request
n8n-nodes-base.httpRequest
From the author
Who it’s for? Anyone calling a Google Cloud Run service from n8n who wants a small, reusable auth layer instead of wiring tokens in every workflow. What it does / How it works This sub-workflow checks whether an incoming idtoken exists and is still valid…