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

# Linking Dropbox Sign as a source

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

> **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)

**Beta release**

This source is currently in **beta**. It works end to end, but you may still hit rough edges. [Let us know](https://us.posthog.com/#panel=support%3Asupport%3Adata_warehouse%3A%3Atrue) if you do.

![](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 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

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 Dropbox Sign, you'll need:

-   **API key** – create one in your [Dropbox Sign API settings](https://app.hellosign.com/home/myAccount#api). 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_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.

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 | — | — |
| `bulk_send_jobs` | A batch of signature requests sent together from a single template. | Full refresh | — | — |
| `faxes` | A fax sent or received on one of the account's fax lines. | Full refresh | — | — |
| `team` | The team the connected account belongs to, with its seat and sub-team counts. Empty when the account is not on a team. | Full refresh | — | — |
| `team_members` | The members of the connected account's team and the role each one holds. Empty when the account is not on a team. | Full refresh | — | — |
| `team_sub_teams` | The direct sub-teams of the connected account's team. Empty when the account is not on a team. | Full refresh | — | — |
| `team_invites` | Invitations to join the connected account's team, with the role each invite grants. Empty when the account is not on a team. | Full refresh | — | — |
| `fax_lines` | A fax line (phone number) on the account, with the accounts that can use it. | 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](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.