> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt

# Linking BoldSign as a source

Canonical URL: https://posthog.com/docs/data-pipelines/sources/boldsign

> **Cloud region:** This page uses US Cloud hosts. For an EU Cloud project, use `https://eu.posthog.com` instead of `https://us.posthog.com` or `https://app.posthog.com` (app host for links).

## On this page

- [Prerequisites](#prerequisites)
- [Adding a data source](#adding-a-data-source)
- [Sync modes](#sync-modes)
- [Configuration](#configuration)
- [Supported tables](#supported-tables)
- [Troubleshooting](#troubleshooting)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_9608fcca70)

![](https://res.cloudinary.com/dmukukwp6/image/upload/texture_tan_dark_a92b0e022d)

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

`npx @posthog/wizard warehouse`

![PostHog Wizard hedgehog](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)

![](https://res.cloudinary.com/dmukukwp6/image/upload/wizard_3f8bb7a240.png)Let AI connect your sources for you

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

1.  In PostHog, go to the [Sources tab](https://app.posthog.com/data-management/sources) of the data pipeline section.
2.  Click **\+ New source** and click **Link** next to this source.
3.  Enter your credentials (see [Configuration](#configuration) below) and click **Next**.
4.  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](https://app.boldsign.com/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_at` timestamp). 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](https://posthog.com/docs/data-pipelines/sources.md#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 |
| `team_documents` | Signature documents across every team the account can see, a wider set than the API user's own documents. | Full refresh | — | documentId |
| `behalf_documents` | Signature documents the API user sent on behalf of another sender identity. | 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 |
| `contact_groups` | Named groups of address-book contacts that can be added to a document together. | Full refresh | — | groupId |
| `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 |
| `custom_fields` | Reusable custom field definitions belonging to a brand, resolving the field identifiers that appear on documents and templates. | Full refresh | — | brandId, customFieldId |

## 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](https://posthog.com/docs/data-warehouse/troubleshooting.md). If that doesn't help, [contact support](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) – we're happy to help.