OpenRuna
Sign in
← Workflows

2. Refresh Pipedrive tokens

29 nodes · stopAndError, supabase, httpRequest, respondToWebhook, webhook

Engine
n8n
Nodes
29
Trigger
scheduled/triggered
Source file
1504_Stopanderror_Code_Automation_Webhook.json

Workflow flow

IntegrationsStopAndErrorSupabaseHTTPRespondToWebhookWebhookIFCodeSet
100%
TRIGGER

Webhook

Webhook

TRIGGER

Receive request

Webhook

TRIGGER

catch Auth code

Webhook

convert clientId and secret to base64

Code

Supabase- look for the record

Supabase

Generate Refresh Token from authcode

HTTP

combine client id and secret

Set

Look for the related record in Supabase

Supabase

Get Pipedrive acess token

HTTP

IF rec not found

IF

IF success

IF

Stop and Error

StopAndError

Insert

Supabase

Update tokns in the record

Supabase

Update thr row with new access token

Supabase

Success

RespondToWebhook

Refresh Access Token

HTTP

Get Pipedrive Token

Supabase

Get contact from Pipedrive

HTTP

Access Token Invalid

IF

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

Browse by integration

stopAndErrorsupabasehttpRequestrespondToWebhookwebhook
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

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

Free n8n workflow: 2. Refresh Pipedrive tokens. 29 nodes across stopAndError, supabase, httpRequest, respondToWebhook, webhook, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

This n8n workflow, "2. Refresh Pipedrive tokens", wires together stopAndError, supabase, httpRequest, respondToWebhook, webhook in 29 nodes. 29 nodes · stopAndError, supabase, httpRequest, respondToWebhook, webhook It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

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

Example output

Imported into n8n, "2. Refresh Pipedrive tokens" exposes 29 configured nodes. Trigger type: scheduled/triggered. Integrations: stopAndError, supabase, httpRequest, respondToWebhook, webhook. Open each node after import to map credentials to your own stopAndError and supabase accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "2. Refresh Pipedrive tokens" JSON into a plain-English runbook, node by node. It can flag where stopAndError rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for stopAndError, supabase, httpRequest, respondToWebhook, webhook. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "2. Refresh Pipedrive tokens" — extract stopAndError IDs and secrets into environment variables without changing the 29-node structure.

Frequently asked questions

How do I import "2. Refresh Pipedrive tokens" 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 "2. Refresh Pipedrive tokens" use?
It uses: stopAndError, supabase, httpRequest, respondToWebhook, webhook. The flow diagram above shows how each service connects across the 29 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 stopAndError and supabase credentials in n8n after import.
What trigger type does "2. Refresh Pipedrive tokens" 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 "2. Refresh Pipedrive tokens" 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 stopAndError, supabase, httpRequest, respondToWebhook, webhook.

Related resources