ActionDropbox SignUpdated September 2026
How do I send a Dropbox Sign request?
Short answer: You can send signature request in Dropbox Sign by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Dropbox Sign Send Signature Request action to a workflow, map its 7 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Title title | string | Required | – |
Email Subject subject | string | Optional | Message subject line. |
Email Message message | string | Optional | – |
Signer Email signer_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Signer Name signer_name | string | Required | – |
File URL (publicly accessible) file_url | string | Required | A fully qualified URL (https://...) for the file url (publicly accessible). |
Test Mode test_mode | options | Optional | – |
Sample request
{"title": "{{trigger.title}}","subject": "e.g. Quick update","message": "{{trigger.message}}","signer_email": "e.g. user@example.com","signer_name": "{{trigger.signer_name}}"}
Returns
{"signature_request": {"title": "Contract","signatures": [{"status_code": "awaiting_signature","signature_id": "sig_abc","signer_email_address": "jane@x.com"}],"is_complete": false,"signing_url": "https://app.hellosign.com/...","signature_request_id": "abc123"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Send Signature Request.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Send Signature Request.
What does the Send Signature Request action do in Dropbox Sign?
Sends a fresh signature request from uploaded documents (not templates) with signers, signing order, and message. For one-off bespoke contracts where you're composing the document each time rather than templating.
What inputs does Send Signature Request require?
Required: Title, Signer Email, Signer Name, File URL (publicly accessible). Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Dropbox Sign returns an error?
The run history shows the failed step with its input and the error message Dropbox Sign returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Send Signature Request support batch operations?
Run Send Signature Request inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Dropbox Sign's rate limits.
More actions
Other Dropbox Sign actions.
Action
Cancel Signature Request
Cancels an in-flight signature request. Pending signers get a cancellation notification. For "wrong recipient, void" or "deal lost mid-signing, abandon" workflows.
ActionGet Signature Request
Returns the signature request with per-signer status, audit trail, and PDF download URLs once complete. The standard lookup before downloading the signed PDF or for checking "did all signers finish yet" before downstream side-effects.
ActionList Signature Requests
Paginated signature requests with filters by status. Useful for "outstanding signature requests >7 days old, send reminder" cadence workflows.
ActionSend with Template
Sends a previously-designed template by template ID, filling in the signer roles and merge fields per send. The recommended path for repeatable contracts (NDAs, employment offers, vendor agreements).