Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Index held / follow enabledBrowse archive
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

Live system map / verified archive

The entire automation, wired and inspectable.

Brand marks identify the operational stack. Focus or select any node to isolate its real incoming and outgoing connections.

20

Nodes

18

Edges

6

Zones

System stack

2 integrations

  • Supabase
  • Pipedrive
Pipedrive Token Refresh Automation interactive execution graphStructural view of 20 workflow nodes and 18 visible connections. Focus any node to inspect its connected path. Parameters and credentials are intentionally excluded.catch Auth code. trigger node, webhook. 0 incoming and 1 outgoing connections.catch Auth codeTRIGGERWEBHOOK0 IN / 1 OUTWebhook. trigger node, webhook. 0 incoming and 1 outgoing connections.WebhookTRIGGERWEBHOOK0 IN / 1 OUTReceive request. trigger node, webhook. 0 incoming and 1 outgoing connections.Receive requestTRIGGERWEBHOOK0 IN / 1 OUTconvert clientId and secret to base64. transform node, code. 1 incoming and 1 outgoing connections.convert clientId and secr…TRANSFORMCODE1 IN / 1 OUTSupabase- look for the record. integration node, supabase. 1 incoming and 1 outgoing connections.Supabase- look for the re…INTEGRATIONSUPABASE1 IN / 1 OUTGet Pipedrive Token. integration node, supabase. 2 incoming and 1 outgoing connections.Get Pipedrive TokenINTEGRATIONSUPABASE2 IN / 1 OUTGenerate Refresh Token from authcode. integration node, httpRequest. 1 incoming and 1 outgoing connections.Generate Refresh Token fr…INTEGRATIONHTTPREQUEST1 IN / 1 OUTcombine client id and secret. transform node, set. 1 incoming and 1 outgoing connections.combine client id and sec…TRANSFORMSET1 IN / 1 OUTGet contact from Pipedrive. integration node, httpRequest. 1 incoming and 1 outgoing connections.Get contact from PipedriveINTEGRATIONHTTPREQUEST1 IN / 1 OUTLook for the related record in Supabase. integration node, supabase. 1 incoming and 1 outgoing connections.Look for the related reco…INTEGRATIONSUPABASE1 IN / 1 OUTGet Pipedrive acess token. integration node, httpRequest. 1 incoming and 1 outgoing connections.Get Pipedrive acess tokenINTEGRATIONHTTPREQUEST1 IN / 1 OUTIF rec not found. decision node, if. 1 incoming and 2 outgoing connections.IF rec not foundDECISIONIF1 IN / 2 OUTIF success. decision node, if. 1 incoming and 2 outgoing connections.IF successDECISIONIF1 IN / 2 OUTRefresh Access Token. integration node, httpRequest. 1 incoming and 1 outgoing connections.Refresh Access TokenINTEGRATIONHTTPREQUEST1 IN / 1 OUTAccess Token Invalid. decision node, if. 1 incoming and 2 outgoing connections.Access Token InvalidDECISIONIF1 IN / 2 OUTInsert. integration node, supabase. 1 incoming and 0 outgoing connections.InsertINTEGRATIONSUPABASE1 IN / 0 OUTUpdate tokns in the record. integration node, supabase. 1 incoming and 0 outgoing connections.Update tokns in the recordINTEGRATIONSUPABASE1 IN / 0 OUTUpdate thr row with new access token. integration node, supabase. 1 incoming and 0 outgoing connections.Update thr row with new a…INTEGRATIONSUPABASE1 IN / 0 OUTStop and Error. integration node, stopAndError. 1 incoming and 0 outgoing connections.Stop and ErrorINTEGRATIONSTOPANDERROR1 IN / 0 OUTSuccess. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.SuccessTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUT

Signal inspector

Focus, hover, or select a node to illuminate its real path.

triggeraidecisiontransformintegration
Scroll horizontally to inspect every zone.verified structural metadata · graph 49511669031b71feEnter or click to lock · Escape to clear

Structured review

Read the workflow as a system, not a node dump.

The archived graph is grouped into operational zones, then checked against the controls needed to adapt the pattern safely. Every count below is derived from the normalized record.

01

Entry signals

4 nodes

Events, schedules, and unconnected roots that can start an execution.

Success

Trigger

Webhook

Trigger

Receive request

Trigger

catch Auth code

Trigger

02

Data & operations

9 nodes

Transformations and external-system actions that move the work forward.

Get Pipedrive Token

Integration

Get contact from Pipedrive

Integration

Refresh Access Token

Integration

convert clientId and secret to base64

Transform

Generate Refresh Token from authcode

Integration

Look for the related record in Supabase

Integration

+ 3 more in system map
03

Intelligence & routing

3 nodes

Model calls and control points that interpret, branch, or govern the run.

Access Token Invalid

Decision

IF rec not found

Decision

IF success

Decision

04

Terminal actions

4 nodes

Nodes with no visible outgoing edge: the workflow’s observable outcomes.

Stop and Error

Integration

Insert

Integration

Update tokns in the record

Integration

Update thr row with new access token

Integration

Provenance boundary

Inspectable does not mean redistributable.

This page publishes structural metadata extracted from a local workflow archive. Parameters, credential references, code bodies, and downloadable JSON are excluded. The route can enter indexing only after a graph match and quality gate; source licensing remains a separate promotion gate.

Graph match
exact
Quality score
13 / 14
Raw download
Held
Crawler state
Follow

Adjacent systems

Keep tracing the stack.

Related records are ranked by shared integrations and graph quality.

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