Skip to Workflow Atlas
Event-Driven AutomationIntermediate

OIDC Client Authentication Workflow

OIDC Client Authentication Workflow is a 12-node automation blueprint connecting OIDC Provider. Inspect its trigger, execution graph, branches, and implementation requirements.

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

12

Nodes

13

Links

1

Run groups

Connected tools

1 integrations

  • OIDC Provider

Canvas controls

Fit wide systems, then zoom into any run group.

OIDC Client Authentication Workflow execution lanes1 run groups containing 12 workflow nodes and 13 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Webhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTSet variables : auth, token, userinfo, client id, scope. transform node, set. 1 incoming and 1 outgoing connections.STEP 02Set variables : auth, tok…TRANSFORMSET1 IN / 1 OUTCode. transform node, code. 1 incoming and 1 outgoing connections.STEP 03CodeTRANSFORMCODE1 IN / 1 OUTIF we have code in URI and not in PKCE mode. decision node, if. 1 incoming and 2 outgoing connections.STEP 04IF we have code in URI an…DECISIONIF1 IN / 2 OUTget access_token from /token endpoint with code. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05get access_token from /to…INTEGRATIONHTTPREQUEST1 IN / 1 OUTIF token is present. decision node, if. 1 incoming and 2 outgoing connections.STEP 05IF token is presentDECISIONIF1 IN / 2 OUTuser info. integration node, httpRequest. 2 incoming and 1 outgoing connections.STEP 06user infoINTEGRATIONHTTPREQUEST2 IN / 1 OUTIF user info ok. decision node, if. 1 incoming and 2 outgoing connections.STEP 07IF user info okDECISIONIF1 IN / 2 OUTWelcome page. integration node, html. 1 incoming and 1 outgoing connections.STEP 08Welcome pageINTEGRATIONHTML1 IN / 1 OUTlogin form. integration node, html. 2 incoming and 1 outgoing connections.STEP 08login formINTEGRATIONHTML2 IN / 1 OUTsend back welcome page. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMEsend back welcome pageTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTsend back login page. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMEsend back login pageTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.12 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

send back welcome page

13 Execution Links
  1. Start

    Webhook

    Trigger

  2. Step 2

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

    Transform

  3. Step 3

    Code

    Transform

  4. Step 4

    IF we have code in URI and not in PKCE mode

    Decision

  5. Step 5

    get access_token from /token endpoint with code

    Integration

    IF token is present

    Decision

  6. Step 6

    user info

    Integration

  7. Step 7

    IF user info ok

    Decision

  8. Step 8

    Welcome page

    Integration

    login form

    Integration

  9. Outcome

    send back welcome page

    Trigger

    send back login page

    Trigger

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.