Accounting & HR
Set up Dropbox Sign
Connect Dropbox Sign (the HelloSign that was) to bring signature requests in as documents — each request's current PDF with its signing state and every signer's standing, who has signed and who is still due, plus your reusable templates — so “do we have the signed agreement with this supplier, and who signed it” answers from the paper itself. Read-only.
Before you start
- The credential is a single API key: in Dropbox Sign (sign.dropbox.com) open Settings → API and generate or reveal it.
- The key reads the account's signature requests and templates. It signs in over HTTP Basic with a blank password, so the key is the only thing to enter.
- Read-only in use: nothing is ever sent, reminded or voided with it.
- Documents → Dropbox Sign, paste the API key.
- Choose access groups, Test, then Sync.
What comes in
- Each signature request as one document — the current PDF, titled with the request's title (or its subject), marked out for signature, complete or declined, and naming every signer: who has signed and who is still awaited.
- Its date is the day of the latest signature; a request nobody has signed yet carries the day it was created.
- The PDF is fetched only when a signer's status moves — an unchanged request is never downloaded again on a sync.
- Templates as their own entries — the title, the signer roles it defines and the files it carries, fetched as a PDF like a request.
- Dropbox Sign never archives requests out of its listing, so every request the account holds is listed, in flight or long complete.
Access
Access is allow-only: Dropbox Sign exposes no per-request viewers of its own, so the access groups chosen when the source is set up cover everything it brings in — every request and template is visible to everyone in those groups.
Completed requests carry the executed agreement's standing; declined ones stay findable but rank last, and one still out for signature counts as pending until everyone has signed. Requests cap at 2,000 and templates at 500 — the listing offers no newest-first order, so when a cap is hit the sync summary says so, up to that many are synced and everything beyond stays as already ingested rather than reading as deleted. The API exposes no modified timestamp for templates, so a template edit that changes neither its title, a signer role nor a file name goes undetected until something else about it changes; the sync summary repeats that once per sync while templates exist. Test signs in, names the account's email address and reports how many requests are reachable; a wrong or deleted key makes it say Dropbox Sign rejected the credentials, and a blank one asks you to set the Dropbox Sign API key.
Last updated 20 Sep 2026