ActionDropbox SignUpdated September 2026
How do I send a Dropbox Sign template?
Short answer: You can send with template in Dropbox Sign by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Dropbox Sign Send with Template action to a workflow, map its 6 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 |
|---|---|---|---|
Template ID template_id | string | Required | – |
Title title | string | Required | – |
Signer Role Name signer_role | string | Required | Client |
Signer Email signer_email | string | Required | The email address. Used as the recipient or identifier depending on context. |
Signer Name signer_name | string | Required | – |
Test Mode test_mode | options | Optional | – |
Sample request
{"template_id": "{{trigger.template_id}}","title": "{{trigger.title}}","signer_role": "Client","signer_email": "e.g. user@example.com","signer_name": "{{trigger.signer_name}}"}
Returns
{"signature_request": {"title": "NDA","signature_request_id": "abc"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Send with Template.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Send with Template.
What does the Send with Template action do in Dropbox Sign?
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).
What inputs does Send with Template require?
Required: Template ID, Title, Signer Role Name, Signer Email, Signer Name. 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 with Template support batch operations?
Run Send with Template 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 Signature Request
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.