Linking Dropbox Sign as a source
This source is currently in alpha. The interface and available tables may change.
The Dropbox Sign connector syncs your Dropbox Sign e-signature data into PostHog, so you can analyze your signature requests and documents alongside your product data.
Prerequisites
You need a Dropbox Sign account with access to create an API key.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
When linking Dropbox Sign, you'll need:
- API key – create one in your Dropbox Sign API settings. The key is used with HTTP Basic authentication (the key as the username, with a blank password).
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
Dropbox Sign exposes no server-side timestamp cursor, so this source is full refresh only.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
signature_requests | A request sent to one or more signers to sign one or more documents. | Full refresh | — | — |
templates | A reusable template that pre-defines documents, signer roles, and fields for signature requests. | Full refresh | — | — |
api_apps | An API application registered under the account, used to embed Dropbox Sign and receive callbacks. | Full refresh | — | — |
account | The Dropbox Sign account connected via the API key. | Full refresh | — | — |
Troubleshooting
- If you see an authentication error, your API key may be invalid or revoked. Create a new API key in your Dropbox Sign API settings, then reconnect.
- If you see a permission error, check the key's permissions and your plan, then reconnect.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.