Contracts built from the request and sent for signature automatically

The scenario takes a request from oneC, builds a formatted contract from its data, sends it to the client for signature, and writes the document id and status back to oneC.

  • The contract is built from the request data — no manual copying
  • It goes out for signature immediately, while the client is still warm
  • The document status is visible in oneC, no inbox archaeology
  • A test environment lets you rehearse without touching live documents
SupabaseDocusign
Set this upScriptera

How it works

To pass leads from oneC to automatically, use a ready-made scenario — no manual copying, no lost leads.

  1. Starts when: Triggered by Another Workflow
  2. Then: Fetch Assessment from Supabase
  3. Then: Compose Contract HTML Code
  4. Then: Encode Contract HTML
  5. Check: Check SBX Environment
  6. If yes: Post to DocuSign JWT API (SBX)
  7. Then: Post for DS Access Token (SBX)
  8. Then: Post to Create DS Envelope (SBX)
  9. Then: Update in Supabase DB
  10. If no: Post to DocuSign JWT API
  11. Then: Post for DocuSign Access Token
  12. Then: Post to Create DocuSign Envelope

You can launch this integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios