Send Signature Request: Dropbox Sign action

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.

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 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 Signature Request support batch operations?

Yes. Run Send Signature Request inside a Loop node to process arrays. Tiny Command handles Dropbox Sign's rate limits automatically so you don't have to throttle manually.

More actions