How to send with template in Dropbox Sign

Send with Template in Dropbox Sign — start free

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Send with Template support batch operations?

Yes. Run Send with Template inside a Loop node to process arrays. TinyCommand handles Dropbox Sign's rate limits automatically so you don't have to throttle manually.

More actions