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.
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 | – |
{"title": "{{trigger.title}}","subject": "e.g. Quick update","message": "{{trigger.message}}","signer_email": "e.g. user@example.com","signer_name": "{{trigger.signer_name}}"}
{"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.
Any of these apps can fire this action as part of a workflow.