Linking Tally as a source

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.

Learn more

Alpha release

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

The Tally connector syncs workspaces, forms, questions, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

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.

Enter a Tally API key to sync your workspaces, forms, folders, questions, submissions, form analytics, and webhooks.

You can create an API key in your Tally settings. No extra scopes are needed.

Submissions are fetched one form at a time and Tally allows 100 requests per minute, so the first sync of an account with many forms can take a while.

You'll be asked for:

API key: for example tly-....

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.

All Tally tables are full refresh. Each sync replaces the contents of the table.

Configuration

Option	Description
`API key` Type: password Required: True
`Submissions to sync` Type: select Required: False	Completed submissions sync incrementally. Including partial ones syncs the whole submissions table on every run, because a partial submission is still being filled in and its submitted time is not a settled cursor. To apply this change to an existing source, use 'Delete table and resync' on the submissions table. 'Sync now' alone won't backfill the submissions you're adding.

Supported tables

Table	Description	Sync method	Incremental field	Primary key
`workspaces`	A workspace groups forms and the members who can access them.	Full refresh	—	—
`forms`	A form or survey, including its publication status and submission count.	Full refresh	—	—
`questions`	A question in a form. Submission answers are keyed by question id, so this table is what makes the submissions table readable.	Full refresh	—	—
`submissions`	A single submission of a form, with every answer nested under `responses`. Answers are keyed by question id, which joins to the questions table.	Incremental, Full refresh	submittedAt	—
`webhooks`	A webhook registered on a form to push form events to an external URL.	Full refresh	—	—
`folders`	A folder used to organize a workspace's forms. Folders can nest under a parent folder.	Full refresh	—	—
`form_analytics_metrics`	Aggregate performance metrics for a form over its whole history. One row per form, recomputed on every sync.	Full refresh	—	—

Troubleshooting

If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

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.