Dropbox Sign
Paste an API keySend generated PDFs out for legally binding signature.
What you can do
- Send for signature with Dropbox Sign — first document of the run goes to one signer
No false success: every send/create in Dropbox Sign is verified — ASHDOCS reads the item back from Dropbox Sign's API before the step turns green. If it can't be found, the run fails honestly instead of pretending.
Get your Dropbox Sign credentials
- 1Log in at hellosign.com and open Settings → API (hellosign.com/home/myAccount#api).
- 2Create or reveal your API key and copy it.
Add the connection in ASHDOCS
- 1Open the Connections page in the flows console.
- 2Click “Connect with a key” and pick Dropbox Sign.
- 3Paste: API key. ASHDOCS validates the credentials against Dropbox Sign before saving — a bad key is rejected with a plain-English reason, never stored.
Use it in a flow
In the flow builder, add the Dropbox Sign step, pick your connection, and fill the fields — values from earlier steps drop in as {{s1.field}} placeholders. Then hit Test this step in the step's panel to run it on its own before switching the flow on.
Troubleshooting
“refused the request” on a free plan
Free API plans can only send with test_mode = yes (set it in the step). Test signatures are not legally binding.
Signer never gets the email
Check the signer email for typos — Dropbox Sign sends the request, not ASHDOCS.
FAQ
Is the request verified?
Yes — the signature request is read back by its ID before the step turns green.
Multiple signers?
One signer per step today. Add a second Dropbox Sign step for a second signer.