List Signature Requests: Dropbox Sign action

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.

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does List Signature Requests support batch operations?

Yes. Run List Signature Requests inside a Loop node to process arrays. Tiny Command handles Dropbox Sign's rate limits automatically so you don't have to throttle manually.

More actions