DocuSign
DocuSign envelope and signature events
DocuSign envelopes carry one or more documents through a signing flow — sent to one or many recipients with a defined signing order, completed when every signer has done their part. Tiny Command surfaces two terminal triggers (Envelope Sent — fired when the envelope leaves draft and starts being delivered to recipients; Envelope Completed — fires when the last recipient signs and the executed PDF is available) and four actions (Send Envelope, Get Envelope, List Envelopes, Void Envelope). The connection uses DocuSign OAuth at user scope, with both demo (sandbox) and production environments selectable at connection time. Send Envelope takes either an embedded template ID with role merge fields, or a raw document base64 with custom tabs (signature, date, text). Envelope Completed is the high-value event: the payload includes the completed-PDF download URL, every recipient's signing certificate (IP, timestamp, auth method), and any custom envelope metadata you set at send time — typically the contract ID you use to round-trip back into your CRM.
Workflows start when DocuSign does.
2 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when the last recipient signs and the envelope completes. Payload includes the envelopeId, signer audit trail, and a pointer to the completed PDF. The hook for "contract signed → provision the customer / update the deal stage / kick off onboarding".
Fires when the envelope leaves draft and starts being delivered to recipients. Useful for pipeline-tracking workflows that log "contract sent" timestamps for sales-process audit and follow-up workflows.
Do anything DocuSign can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Get Envelope | Returns the envelope with per-recipient status, audit trail, and documents. The standard lookup for "is the envelope signed yet?" polling workflows or for round-tripping back to fetch the completed PDF. |
| List Envelopes | Returns paginated envelopes with filters by status, sender, recipient email, time range. Useful for "all outstanding contracts" reporting and for "envelopes idle 7+ days" reminder workflows. |
| Send Envelope | Creates and sends an envelope from a template or raw document. Optional templateRoles map template roles to actual signer emails. The standard contract-send workflow once you have the template designed in DocuSign admin. |
| Void DocuSign Envelope | Voids an in-flight envelope with a required voidedReason string. Recipients who haven't signed receive a void notification. Useful for "wrong recipient, abort" workflows or "terms changed before signing, restart" cases. |
Pre-built DocuSign workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect DocuSign once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every DocuSign field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the DocuSign integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect DocuSign to Tiny Command?
What DocuSign triggers does Tiny Command support?
What DocuSign actions can I run from a workflow?
Is the DocuSign integration real-time?
Do I need to write code to use DocuSign with Tiny Command?
How much does the DocuSign integration cost?
More other apps people connect.
Same category as DocuSign, ordered by how often teams pair them. Hover the carousel to pause.
Do more with DocuSign.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
