Short answer: Drop the "Dropbox Sign → Send with Template" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 | — |
{"template_id": "{{trigger.template_id}}","title": "{{trigger.title}}","signer_role": "Client","signer_email": "e.g. user@example.com","signer_name": "{{trigger.signer_name}}"}
{"signature_request": {"title": "NDA","signature_request_id": "abc"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.