Send DocuSign envelopes with Supabase contract data

by Pedro Olavarria ✓ · 6 views · created 2026-07-01 · Document Extraction

What this workflow does

This workflow has 12 nodes and runs when another workflow calls it. Along the way it connects Supabase. It also calls account-d.docusign.com and account.docusign.com over HTTP.

How it runs

Trigger: When another workflow calls it.

1. Fetch Assessment from Supabase (Supabase): get many
2. Compose Contract HTML Code (Code): runs custom JavaScript code
3. Encode Contract HTML (Code): runs custom JavaScript code
4. Check SBX Environment (If): checks a condition and branches into true / false
5. Post to DocuSign JWT API (SBX) (HTTP Request): calls an HTTP API (POST)
6. Post to DocuSign JWT API (HTTP Request): calls an HTTP API (POST)
7. Post for DS Access Token (SBX) (HTTP Request): calls account-d.docusign.com (POST)
8. Post for DocuSign Access Token (HTTP Request): calls account.docusign.com (POST)
9. Post to Create DS Envelope (SBX) (HTTP Request): calls an HTTP API (POST)
10. Post to Create DocuSign Envelope (HTTP Request): calls an HTTP API (POST)

…plus 1 more step. See the full node list below.

Services it uses

Supabase

HTTP calls to: account-d.docusign.com, account.docusign.com

Before you upgrade to n8n 3.0

Nodes used (5)

• Execute Workflow Triggern8n-nodes-base.executeWorkflowTrigger
• HTTP Requestn8n-nodes-base.httpRequest
• Coden8n-nodes-base.code
• Supabasen8n-nodes-base.supabase
• Ifn8n-nodes-base.if

From the author

Quick overview This workflow is triggered by another n8n workflow, fetches an assessment record from Supabase, generates an HTML contract, and sends it as a DocuSign envelope using JWT authentication in either production or sandbox based on the recipient…

View the original on n8n.io → Check your own copy