ActionDropbox SignUpdated September 2026

How do I list Dropbox Sign requests?

Short answer: You can list signature requests in Dropbox Sign by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Dropbox Sign List Signature Requests action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Signature Requests in Dropbox Sign — start free All 5 Dropbox Sign actions

List Signature Requests 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
Page page	string	Optional	–
Page Size page_size	string	Optional	–
Query filter query	string	Optional	–

Sample request

{
  "page": "{{trigger.page}}",
  "page_size": "{{trigger.page_size}}",
  "query": "{{trigger.query}}"
}

Returns

{
  "list_info": {
    "num_pages": 1
  },
  "signature_requests": [
    {
      "title": "Contract",
      "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 List Signature Requests.

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 List Signature Requests.

What does the List Signature Requests action do in Dropbox Sign?

Paginated signature requests with filters by status. Useful for "outstanding signature requests >7 days old, send reminder" cadence workflows.

What inputs does List Signature Requests require?

List Signature Requests has no required inputs. Sensible defaults are applied if you leave fields blank.

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

Run List Signature Requests 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