ActionDropbox SignUpdated September 2026

How do I fetch a Dropbox Sign request status?

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.

Get Signature Request in Dropbox Sign — start free All 5 Dropbox Sign actions

Get Signature Request 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
Signature Request ID request_id	string	Required	–

Sample request

{
  "request_id": "{{trigger.request_id}}"
}

Returns

{
  "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.

Triggered by

Apps that pair well as the trigger for Get Signature Request.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Dropbox Sign

2 Google Sheets triggers

HubSpot → Dropbox Sign

18 HubSpot triggers

FAQ

Questions about Get Signature Request.

What does the Get Signature Request action do in Dropbox Sign?

Returns the signature request with per-signer status, audit trail, and PDF download URLs once complete. The standard lookup before downloading the signed PDF or for checking "did all signers finish yet" before downstream side-effects.

What inputs does Get Signature Request require?

Required: Signature Request ID. 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 run history shows the failed step with its input and the error message Dropbox Sign returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get Signature Request support batch operations?

Run Get Signature Request inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Dropbox Sign's rate limits.

More actions