Linking DocuSeal as a source

Alpha release

This source is currently in alpha. The interface and available tables may change.

The DocuSeal connector syncs your document signing data – templates, submissions, and submitters – into the PostHog Data warehouse, so you can analyze your signing workflows alongside your product data.

Prerequisites

You need a DocuSeal account with access to create an API key. The key has full account access, as DocuSeal does not offer per-resource scopes. Self-hosted deployments are not supported yet.

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

API key – create one under Settings → API in your DocuSeal console.
Region – pick the region your DocuSeal account is hosted in, either Global (api.docuseal.com) or EU (api.docuseal.eu).

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 for a full explanation of how each mode works and how to choose between them.

This source is full-refresh only. DocuSeal has no server-side timestamp filter, and its records mutate as submission statuses change, so every table is fully re-synced on each run.

Configuration

Option	Type	Required
`API key`	password	Yes
`Region`	select	Yes

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`templates`	A reusable document template with the fields submitters fill in to create submissions.	Full refresh	—	—
`submissions`	A signing request created from a template, grouping the submitters and documents involved.	Full refresh	—	—
`submitters`	An individual party on a submission who fills in fields and signs the document.	Full refresh	—	—

Troubleshooting

If you see an authentication error, your API key is invalid or has been revoked. Create a new key in your DocuSeal account settings, then reconnect.
If you see a permissions error, the key does not have access to this data. Check the key in your DocuSeal account settings, 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.