Short answer: You can get signature request in Dropbox Sign by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Dropbox Sign Get Signature Request action to a workflow, map its 1 input 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 |
|---|---|---|---|
Signature Request ID request_id | string | Required | – |
{"request_id": "{{trigger.request_id}}"}
{"signature_request": {"files_url": "https://.../files","is_complete": true,"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.