Typeform
Connect Typeform as a webhook data source: how you paste Instasent's webhook URL into a Typeform so responses flow into the Instasent ingest stream, what it syncs, how fields map to attributes, and how consent is controlled through the data you send.
Typeform is a webhook platform: rather than reading your data directly, you paste Instasent's webhook URL into a Typeform so its responses flow into Instasent's ingest stream. Use it to add the contacts your surveys capture to your audience.
How to connect
Typeform is a webhook platform: you don't create a credential — Instasent gives you a webhook URL, and you paste it into your Typeform. This is a manual webhook: Typeform posts to that URL on every response. You can create the Instasent source before setting anything up in Typeform; the source waits for data in real time.
Add the data source
In Data sources, select Add data source and choose Typeform 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 Typeform
In your Typeform's Connect / webhooks settings, add a webhook and paste the Instasent webhook URL. From now on Typeform posts each response 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
Typeform sends the contacts its surveys capture — one per response — in real time
as each one comes in. The payload identifies the contact (contact_id) and carries the
answers the survey collected.
Field mapping
The fields Typeform sends are mapped to Instasent attributes the same way as any source — you confirm which incoming answers go into which Instasent attributes. See field mapping.
Consent mapping
Typeform passes through the answers the survey collects; it has no consent mapping of its
own. Consent is controlled by the fields you map — if a survey 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.