OpenRuna
Sign in
← Workflows

OIDC client workflow

15 nodes · webhook, httpRequest, respondToWebhook, html

Engine
n8n
Nodes
15
Trigger
scheduled/triggered
Source file
2034_Code_Webhook_Automate_Webhook.json

Workflow flow

IntegrationsWebhookHTTPRespondToWebhookHtmlCodeIFSet
100%
TRIGGER

Webhook

Webhook

Set variables : auth, token, userinfo, client id, scope

Set

Code

Code

IF we have code in URI and not in PKCE mode

IF

IF token is present

IF

get access_token from /token endpoint with code

HTTP

user info

HTTP

IF user info ok

IF

Welcome page

Html

login form

Html

send back login page

RespondToWebhook

send back welcome page

RespondToWebhook

12 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

OIDC client workflow is a free n8n workflow on OpenRuna — 15 nodes connecting webhook, httpRequest, respondToWebhook, html. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

"OIDC client workflow" is an n8n automation built from 15 nodes spanning webhook, httpRequest, respondToWebhook, html. 15 nodes · webhook, httpRequest, respondToWebhook, html A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Benchmark it against your current webhook integration to spot missing steps or redundant nodes.
  • Fork it to add error handling, retries, or a notification step without designing the 15-node flow from scratch.
  • Use it as a starting template when wiring webhook, httpRequest, respondToWebhook, html — adjust node parameters to your accounts and record IDs.
  • Import "OIDC client workflow" into n8n, reconnect credentials for webhook, httpRequest, respondToWebhook, html, and run the same automation in your own workspace.

Example output

Imported into n8n, "OIDC client workflow" exposes 15 configured nodes. Trigger type: scheduled/triggered. Integrations: webhook, httpRequest, respondToWebhook, html. Reconnect the webhook credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "OIDC client workflow" into Claude and ask it to explain each of the 15 nodes. Claude is good at suggesting credential mappings for webhook, httpRequest, respondToWebhook, html, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "OIDC client workflow" to your accounts — which webhook, httpRequest, respondToWebhook, html credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 15 nodes.

Frequently asked questions

How do I import "OIDC client workflow" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "OIDC client workflow" use?
It uses: webhook, httpRequest, respondToWebhook, html. The flow diagram above shows how each service connects across the 15 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own webhook and httpRequest credentials in n8n after import.
What trigger type does "OIDC client workflow" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "OIDC client workflow" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for webhook, httpRequest, respondToWebhook, html.

Related resources