Linking BoldSign as a source
This source is currently in alpha. The interface and available tables may change.
The BoldSign connector syncs your eSignature data – documents, templates, and contacts – into PostHog, so you can analyze your signing workflows alongside your product data.
Prerequisites
You need a BoldSign account with access to its account settings so you can create an API key, and you need to know which region your account is hosted in.
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 BoldSign, you'll need:
- API key – create one in your BoldSign account settings under API → API Key. API keys carry all scopes by default.
- Region – pick the region your BoldSign account lives in. Accounts are hosted on either the US (
api.boldsign.com) or EU (api-eu.boldsign.com) host.
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.
BoldSign tables are full refresh only.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
documents | Signature documents sent from the account, including their status, signers, and lifecycle dates. | Full refresh | — | documentId |
templates | Reusable document templates defined in the account. | Full refresh | — | documentId |
users | Users belonging to the BoldSign account, including their team and role. | Full refresh | — | userId |
teams | Teams configured in the BoldSign account. | Full refresh | — | teamId |
contacts | Address-book contacts available when preparing documents. | Full refresh | — | id |
sender_identities | Verified sender identities that documents can be sent on behalf of. | Full refresh | — | id |
brands | Branding configurations (logos, colors, disclaimers) applied to documents. | Full refresh | — | brandId |
Troubleshooting
- If your API key is invalid or has been revoked, create a new key in your BoldSign account settings, then reconnect.
- If your API key does not have permission to access the data, check the key's permissions, 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.