Secure Google Cloud Run API Calls with Service Account Auth

Securely invoke Google Cloud Run endpoints from n8n using Service Account ID tokens, avoiding public exposure for safe, authenticated API calls.

n8n
Secure Google Cloud Run API Calls with Service Account Auth

This workflow provides a secure method to call Google Cloud Run APIs from n8n without making endpoints publicly accessible. It uses a main workflow that invokes a sub-workflow to generate a Google ID token via Service Account authentication, merges it with request context, and sends authenticated HTTP requests to your Cloud Run service. Ideal for running custom logic like scraping or data processing in containerized environments on Cloud Run's free tier.

Benefits include enhanced security through Cloud IAM (no API keys in n8n), cost-efficiency (no servers needed), and seamless integration for single calls or batched operations. It's perfect for developers automating tasks requiring specialized libraries unavailable in n8n, such as Python scripts in Docker on Cloud Run.

Setup involves creating an authenticated Cloud Run service, a Service Account with 'Cloud Run Invoker' role, downloading the private key JSON, and configuring n8n's JWT (PEM) credential. Update variables for service URL/path, customize HTTP method/body, and follow in-workflow sticky notes for options like looping over items.

Use cases: Securely process data with custom Cloud Run services for web scraping, ML inference, or backend logic; integrate with n8n automations for IT/DevOps pipelines without hosting overhead.

$14.99
Last updated October 3, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Utilities workflows

More from Jordi Faber

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.