Linking Paperform as a source

Alpha release

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

The Paperform connector syncs your forms, fields, submissions, partial submissions, products, coupons, and spaces into the PostHog Data warehouse, so you can analyze form performance and respondent answers alongside your product data.

Prerequisites

You need a Paperform account on a plan that includes API access (Pro, Business, or Agency). The spaces table additionally requires a Business or Agency plan; if your plan doesn't include it, deselect that table when choosing what to sync.

Adding a data source

  1. In PostHog, go to the Sources tab of the data pipeline section.
  2. Click + New source and click Link next to this source.
  3. Enter your credentials (see 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 Paperform, you'll need:

  • API key – create one under Account → Developer in your Paperform account. The key is account-wide and grants read access to your forms and their data.

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.

The submissions table supports incremental syncs on created_at_utc – submissions never change once made, so incremental is the recommended mode for it. The other tables are full refresh only: Paperform's API filters by creation time only, and records like forms and partial submissions keep changing after they're created, so a creation-time cursor would miss their updates.

Configuration

OptionTypeRequired
API keypasswordYes

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
forms

A Paperform form with its slugs, sharing URLs, tags, and submission count.

Full refresh
form_fields

A field (question) on a Paperform form, such as a text input, dropdown, or signature.

Full refresh
submissions

A completed submission to a Paperform form, including the answers, device, and any charge.

Incremental, Full refreshcreated_at_utc
partial_submissions

An in-progress (not yet submitted) response to a Paperform form, with the answers so far.

Full refresh
products

A product sold through a Paperform form's payment fields.

Full refresh
coupons

A discount coupon configured on a Paperform form.

Full refresh
spaces

A Paperform space used to organize forms. Requires a Business or Agency plan.

Full refresh

Troubleshooting

  • If you see an authentication error, your API key is invalid or has been revoked. Create a new key under Account → Developer in Paperform, then reconnect.
  • If you see a permissions error, your Paperform plan doesn't include access to that data. API access requires a Pro, Business, or Agency plan, and the spaces table requires a Business or Agency plan.

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.

Community questions

Was this page useful?

Questions about this page? or post a community question.