Dropbox Sign
DocumentsSend documents for legally binding e-signature with Dropbox Sign. Agents kick off signature requests from file URLs or reusable templates, track signing progress, remind slow signers, cancel in-flight requests, and retrieve the fully signed PDF.
What This Integration Enables
E-signature is a state machine wearing a legal document: sent, viewed, signed, declined, complete. Dropbox Sign exposes that machine cleanly, and this connector hands it to FlowRunner agents so the states drive workflows instead of anxiety. Agents send requests from file URLs or reusable templates with roles and prefilled fields, track per-signer progress, remind the signer whose turn it is, cancel requests that events have overtaken, and retrieve the executed PDF the moment the last signature lands. The operating principle: the document's content is decided by people, and everything about its journey is decided by the workflow. Templates make that split enforceable, because the layout and fields were approved once, and agents only fill in the variables. - Contracts, NDAs, and offer letters dispatch from templates with signer roles resolved from the triggering record - Signing order is honored, so multi-party agreements move sequentially without a coordinator - Per-signer status feeds SLA logic: reminders, escalations, and decline alerts happen on time, every time - Test Mode lets new workflows rehearse end to end without consuming quota or creating binding requests - Completed documents archive themselves, with Get Account keeping an eye on remaining quota Signature requests are legal instruments in flight, and two operations on them are consequential enough for FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) layer: the send that binds and the cancel that cannot be undone.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The contract that sends itself when the deal is ready
A [HubSpot](/integrations/hubspot) deal moves to contract. The agent reads the template's roles with Get Template, maps the deal contact to the customer role and the sales lead to the countersigner, prefills value and term fields, and fires Send With Template. Polling via Get Signature Request tracks each signer. The rep finds out about a decline in minutes, not at the end-of-week pipeline review, and the deal record always reflects the document's true state.
The signature chase that runs without a chaser
Each morning the agent runs List Signature Requests, filters to incomplete, and checks each one's age against its SLA. Signers whose turn it is and who are past threshold get Send Reminder. The outstanding list, request title, waiting signer, days pending, logs to [Google Sheets](/integrations/google-sheets) and posts to [Slack](/integrations/slack). Follow-up stops depending on someone's memory, and the weekly report on where deals are stuck writes itself as a side effect.
Executed documents that file themselves
When Get Signature Request reports complete, the agent calls Get Signed Document for the merged PDF's temporary URL, uploads the file to [Google Drive](/integrations/google-drive) under the deal's folder with a canonical name, and posts the completion to the team channel. The time-limited URL never gets lost because it is consumed immediately, and at renewal time the executed agreement is exactly where the naming convention says it is.
Human-in-Loop Highlight
Cancel Signature Request cannot be undone, and its blast radius is a legal process already in motion: signers can no longer sign, and a half-executed agreement dies where it stood. An agent watching a CRM might reasonably infer that a deal marked lost should have its contract cancelled, and be wrong, because the stage change was a rep's misclick or the buyer's signature was minutes away. So cancellation in FlowRunner is always a proposal: the agent presents the request's current state from Get Signature Request, who has already signed, who is pending, and the triggering event, and the deal owner confirms before the cancel fires. The initial send of a binding request gets the same respect on non-template paper, since Send Signature Request puts legal language in front of a counterparty. Test Mode exists so workflows can rehearse; production sends and cancels answer to a person.
Agent Capabilities
10 actionsSignature Requests
7- Send Signature Request Sends a new signature request from one or more source documents referenced by public file URLs. Provide a title, an email subject/message, and an ordered list of signers (each with email address and name). Signing order is honored when order values are supplied. Set Test Mode to true to send a non-legally-binding request that does not consume quota. Returns the created signature_request object including its ID and per-signer signature IDs.
- Send With Template Sends a signature request generated from one or more reusable templates. Assign signers to template roles by role name, and optionally prefill named custom fields. Use this instead of Send Signature Request when the document layout and fields are already defined in a Dropbox Sign template. Returns the created signature_request object.
- List Signature Requests Lists signature requests on your account with pagination. Optionally filter with a search query (e.g. by title, signer, or status keywords such as "complete"). Returns the list_info pagination metadata and an array of signature_request objects.
- Get Signature Request Retrieves the full status and details of a single signature request by its ID, including completion state and each signer's status (awaiting, signed, declined). Use this to track progress after sending.
- Send Reminder Sends a reminder email to a specific signer who has not yet signed a signature request, identified by the signer's email address. Only signers whose turn it is (per signing order) can be reminded. Returns the current signature_request object.
- Cancel Signature Request Cancels an incomplete signature request by its ID. Signers can no longer sign a cancelled request. This action cannot be undone and only works on requests that are not already complete. Returns an empty success response.
- Get Signed Document Returns a temporary download URL for the documents in a signature request. By default returns a merged PDF; choose ZIP to get the files as a ZIP archive. The returned file_url is time-limited and points to the current state of the documents (fully signed once the request is complete).
Templates
2- List Templates Lists reusable templates on your account with pagination and an optional search query. Templates define document layouts, signer roles, and fields that Send With Template fills in. Returns list_info pagination metadata and an array of template objects.
- Get Template Retrieves a single template by its ID, including its signer roles, CC roles, named custom fields, and document metadata. Use this to discover the role names and fields required before calling Send With Template.
Account
1- Get Account Returns information about the authenticated Dropbox Sign account, including account ID, email address, role, and signature quota usage. Useful for verifying credentials and checking remaining quota before sending requests.
Frequently Asked Questions
What can FlowRunner do with Dropbox Sign?
FlowRunner agents can run Send Signature Request, Send With Template, and List Signature Requests in Dropbox Sign, plus 7 more actions.
Does connecting Dropbox Sign to FlowRunner require OAuth?
No. Dropbox Sign connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Dropbox Sign trigger a FlowRunner workflow automatically?
Dropbox Sign doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Dropbox Sign
$100 in credits. No card required. Connect in minutes.