Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Pipedrive Token Refresh Automation

Pipedrive Token Refresh Automation is a 20-node automation blueprint connecting Supabase, Pipedrive. Inspect its trigger, execution graph, branches, and implementation requirements.

SupabasePipedrive

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.

20

Nodes

18

Links

3

Run groups

Connected tools

2 integrations

  • Supabase
  • Pipedrive

Canvas controls

Fit wide systems, then zoom into any run group.

Pipedrive Token Refresh Automation execution lanes3 run groups containing 20 workflow nodes and 18 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.catch Auth code. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTcatch Auth codeTRIGGERWEBHOOK0 IN / 1 OUTconvert clientId and secret to base64. transform node, code. 1 incoming and 1 outgoing connections.STEP 02convert clientId and secr…TRANSFORMCODE1 IN / 1 OUTGenerate Refresh Token from authcode. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Generate Refresh Token fr…INTEGRATIONHTTPREQUEST1 IN / 1 OUTLook for the related record in Supabase. integration node, supabase. 1 incoming and 1 outgoing connections.STEP 04Look for the related reco…INTEGRATIONSUPABASE1 IN / 1 OUTIF rec not found. decision node, if. 1 incoming and 2 outgoing connections.STEP 05IF rec not foundDECISIONIF1 IN / 2 OUTInsert. integration node, supabase. 1 incoming and 0 outgoing connections.OUTCOMEInsertINTEGRATIONSUPABASE1 IN / 0 OUTUpdate tokns in the record. integration node, supabase. 1 incoming and 0 outgoing connections.OUTCOMEUpdate tokns in the recordINTEGRATIONSUPABASE1 IN / 0 OUTWebhook. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTWebhookTRIGGERWEBHOOK0 IN / 1 OUTSupabase- look for the record. integration node, supabase. 1 incoming and 1 outgoing connections.STEP 02Supabase- look for the re…INTEGRATIONSUPABASE1 IN / 1 OUTcombine client id and secret. transform node, set. 1 incoming and 1 outgoing connections.STEP 03combine client id and sec…TRANSFORMSET1 IN / 1 OUTGet Pipedrive acess token. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 04Get Pipedrive acess tokenINTEGRATIONHTTPREQUEST1 IN / 1 OUTIF success. decision node, if. 1 incoming and 2 outgoing connections.STEP 05IF successDECISIONIF1 IN / 2 OUTUpdate thr row with new access token. integration node, supabase. 1 incoming and 0 outgoing connections.OUTCOMEUpdate thr row with new a…INTEGRATIONSUPABASE1 IN / 0 OUTStop and Error. integration node, stopAndError. 1 incoming and 0 outgoing connections.OUTCOMEStop and ErrorINTEGRATIONSTOPANDERROR1 IN / 0 OUTReceive request. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTReceive requestTRIGGERWEBHOOK0 IN / 1 OUTGet Pipedrive Token. integration node, supabase. 2 incoming and 1 outgoing connections.STEP 02Get Pipedrive TokenINTEGRATIONSUPABASE2 IN / 1 OUTGet contact from Pipedrive. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 03Get contact from PipedriveINTEGRATIONHTTPREQUEST1 IN / 1 OUTAccess Token Invalid. decision node, if. 1 incoming and 2 outgoing connections.STEP 04Access Token InvalidDECISIONIF1 IN / 2 OUTRefresh Access Token. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Refresh Access TokenINTEGRATIONHTTPREQUEST1 IN / 1 OUTSuccess. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMESuccessTRIGGERRESPONDTOWEBHOOK1 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.20 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

catch Auth code

6 Execution Links

  1. Start

    catch Auth code

    Trigger

  2. Step 2

    convert clientId and secret to base64

    Transform

  3. Step 3

    Generate Refresh Token from authcode

    Integration

  4. Step 4

    Look for the related record in Supabase

    Integration

  5. Step 5

    IF rec not found

    Decision

  6. Outcome

    Insert

    Integration

    Update tokns in the record

    Integration

02

Run Group

Webhook

6 Execution Links

  1. Start

    Webhook

    Trigger

  2. Step 2

    Supabase- look for the record

    Integration

  3. Step 3

    combine client id and secret

    Transform

  4. Step 4

    Get Pipedrive acess token

    Integration

  5. Step 5

    IF success

    Decision

  6. Outcome

    Update thr row with new access token

    Integration

    Stop and Error

    Integration

03

Run Group

Receive request

6 Execution Links

  1. Start

    Receive request

    Trigger

  2. Step 2

    Get Pipedrive Token

    Integration

  3. Step 3

    Get contact from Pipedrive

    Integration

  4. Step 4

    Access Token Invalid

    Decision

  5. Step 5

    Refresh Access Token

    Integration

  6. Outcome

    Success

    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.

Create a build planReturn to the atlas