The flow
Starts it 1Logic 3Service 8
The steps in the order they run, from what starts it.
- 1Triggered by Another WorkflowExecute Workflow triggerStarts it
- 2Fetch Assessment from SupabaseSupabaseService
- 3Compose Contract HTML CodeCodeLogic
- 4Encode Contract HTMLCodeLogic
- 5Check SBX EnvironmentIfLogic
- 6Post to DocuSign JWT API (SBX)Http RequestService
- 7Post to DocuSign JWT APIHttp RequestService
- 8Post for DS Access Token (SBX)Http RequestService
- 9Post for DocuSign Access TokenHttp RequestService
- 10Post to Create DS Envelope (SBX)Http RequestService
- 11Post to Create DocuSign EnvelopeHttp RequestService
- 12Update in Supabase DBSupabaseService
How it's built
- Starts on
- An event in a connected app
- Steps
- 12, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Supabase
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Supabase account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 12 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 12 steps before you point it at anything that matters.