ActionDropbox SignUpdated September 2026

How do I cancel a Dropbox Sign request?

Short answer: You can cancel signature request in Dropbox Sign by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Dropbox Sign Cancel 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.

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

Cancel 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

{}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Cancel 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 Cancel Signature Request.

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

Cancels an in-flight signature request. Pending signers get a cancellation notification. For "wrong recipient, void" or "deal lost mid-signing, abandon" workflows.

What inputs does Cancel 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 Cancel Signature Request support batch operations?

Run Cancel 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