Paperform
Connect Paperform as a webhook data source: how you paste Instasent's webhook URL into a Paperform form so submissions flow into the Instasent ingest stream, what it syncs, how fields map to attributes, and how consent is controlled through the data you send.
Paperform is a webhook platform: rather than reading your data directly, you paste Instasent's webhook URL into a Paperform form so its submissions flow into Instasent's ingest stream. Use it to add the contacts your forms capture to your audience.
How to connect
Paperform is a webhook platform: you don't create a credential — Instasent gives you a webhook URL, and you paste it into your form. This is a manual webhook: Paperform posts to that URL on every submission. You can create the Instasent source before setting anything up in Paperform; the source waits for data in real time.
Add the data source
In Data sources, select Add data source and choose Paperform from the Integrations section.
Configure the source
Fill in the Configure step — Connection name, Default country, Regional settings / Locale and Timezone — and Instasent creates the source.
Copy the webhook URL
Instasent shows the source's Webhook URL under Setup instructions. Copy it.
Paste it into your Paperform form
In your form's configuration, add a webhook and paste the Instasent webhook URL. From now on Paperform posts each submission to Instasent.
Watch the stream log
Back in Instasent, the source shows a stream log of the data arriving, so you can confirm the connection is working.
For the endpoint shapes and the full setup, see API & webhooks.
What it syncs
Paperform sends the contacts its forms capture — one per submission — in real time
as each one comes in. The payload identifies the contact (contact_id) and carries the
fields the form collected.
Field mapping
The fields Paperform sends are mapped to Instasent attributes the same way as any source — you confirm which incoming values go into which Instasent attributes. See field mapping.
Consent mapping
Paperform passes through the fields the form collects; it has no consent mapping of its
own. Consent is controlled by the fields you map — if a form collects an explicit
marketing opt-in and you map it to a consent attribute, that value applies. The same
rules apply as for any import: only set _accepts_marketing_* to false on an active
opt-out; "no data" stays null. See
Consent.