Linking Yousign as a source
This source is currently in alpha. The interface and available tables may change.
The Yousign connector syncs your eSignature data – signature requests, signers, documents, contacts, users, workspaces, and labels – into PostHog, so you can analyze signing funnels and completion rates alongside your product data.
Prerequisites
You need a Yousign account on a plan with API access (Plus, Pro, or Scale) and an API key. Yousign API keys are environment-scoped: a sandbox key can only read sandbox data and a production key can only read production data.
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.
You need two things to connect Yousign:
- API key: in the Yousign app, go to Integrations → API keys and create a key. A read-only, organization-scoped key is enough for syncing; automatic webhook creation additionally requires a full-access key.
- Environment: pick the environment your key belongs to – Production or Sandbox.
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.
The signature_requests table supports incremental syncs using Yousign's server-side date filters on created_at, activated_at, or completed_at. Syncing on created_at only picks up new requests, so if you care about status changes on existing requests, either enable webhook sync (recommended) or sync incrementally on completed_at with an occasional full refresh.
The signers and documents tables are fetched one signature request at a time, so a sync issues at least one request per signature request. With Yousign's standard rate limits this can make full refreshes slow on large accounts – schedule them accordingly.
Webhooks for real-time syncing
When you select the webhook sync method for signature_requests, PostHog creates a webhook subscription in your Yousign account automatically (this requires a full-access API key). Yousign signs webhook deliveries, and PostHog verifies the signature using the subscription's secret key, which is captured automatically when the webhook is created.
To set the webhook up manually instead: in the Yousign app, go to Integrations → Webhooks, create a subscription pointing at the webhook URL shown in PostHog, subscribe to the signature_request.* lifecycle events, then copy the subscription's secret key into the signing secret field in PostHog.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Environment | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
signature_requests | One row per signature request, with embedded signer, approver, and document ids and their statuses. | Webhook, Incremental, Full refresh | created_at, activated_at, completed_at | — |
signers | Signer details for every signature request, one row per signer. | Full refresh | — | — |
documents | Document metadata for every signature request, one row per document. | Full refresh | — | — |
contacts | Contacts saved in the organization's contact book. | Full refresh | — | — |
users | Members of the Yousign organization. | Full refresh | — | — |
workspaces | Workspaces in the Yousign organization. | Full refresh | — | — |
labels | Labels used to organize signature requests. | Full refresh | — | — |
Troubleshooting
- Yousign rejected the API key: check the key is copied correctly and hasn't been revoked, and that the environment matches the key – a sandbox key cannot access the production API and vice versa.
- Missing signature requests: workspace-scoped API keys only see their workspace's data. Reconnect with an organization-scoped key to sync everything.
- Webhook creation failed: webhook management requires a full-access API key. Either reconnect with one or create the subscription manually as described above.
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.