Documentation menu

Typeform: your respondents

Add the people who answer your Typeform form to Mailcheer: a webhook on every response, a test request, and picking the email field in a few clicks.

Every time someone submits your form, Typeform can send their answers to a web address within seconds. That is a webhook. Give it your Mailcheer inbound webhook URL and the respondent lands in your contacts, with no export and no import.

Before you start

  • A Mailcheer inbound webhook. In Mailcheer, open Integrations → Bring in contacts and click Create an inbound webhook. Mailcheer gives you an address that looks like https://mailcheer.com/api/in/<token>. Treat it as a secret and never publish it: anyone who has it can send data to it.
  • A Typeform plan that includes webhooks. On its pricing page, Typeform lists "Webhooks & integrations" among the features of the Basic plan, and the Plus and Business plans include everything in Basic. To check what your own plan includes, Typeform points you to your Organization Settings.
  • A question that asks for the email address. The simplest option is an Email question.

Only bring in people who have agreed to receive your emails, and say so clearly in your form. Double opt-in (a confirmation email) is on by default in Mailcheer.

1. Create the webhook in Typeform

  1. Open your form from your Workspace.
  2. Go to the Connect panel, then the Webhooks tab.
  3. Click Add a webhook.
  4. Paste your Mailcheer inbound webhook URL into Destination URL, then click Save webhook.
  5. Back on the Webhooks tab, switch the webhook on with its toggle. A new webhook stays Off until you turn it on.

Typeform only accepts https:// addresses, and your Mailcheer address is one.

The Edit button next to the webhook opens its settings. Two of them matter here:

  • Secret: optional. Typeform uses it to sign what it sends. You can leave it empty.
  • Trigger: choose completed responses. If you add partial responses, the same person can trigger the webhook more than once.

Click Save changes when you are done.

2. Send a test

  1. On the Webhooks tab, click View deliveries.
  2. Click Send test request.
  3. The delivery shows up in the list on the left, marked Test. Request shows what Typeform sent; Response shows what came back.
  4. Close the window with the X in the top right corner.

To send a test again, the webhook must be On. You can also fill in the form yourself with your own email address: a real response takes exactly the same path.

Mailcheer replies right away and processes the delivery afterwards.

3. Pick your fields in Mailcheer

Go back to your inbound webhook in Mailcheer. It shows what it received, along with the list of fields it found.

Typeform puts the answers inside form_response, in a list called answers. Each answer states its type, and the answer to an Email question has the type email. That is the field to look for.

Then choose, with a click:

  • the field that holds the email (required);
  • the first name and last name, if you want them;
  • tags: fixed ones (such as typeform) or taken from a field;
  • double opt-in, on by default;
  • the automation to trigger, if you have one.

To bring in people you already have, use a file instead: see Import your contacts.

If it does not work

Start by looking at what Typeform sent: Webhooks tab → View deliveries. Typeform keeps deliveries for 30 days, along with the response to each one.

  • The webhook is Off. New webhooks start switched off. Turn it on from the Webhooks tab.
  • The address is incomplete. Open Edit and compare Endpoint URL with the inbound webhook URL shown in Mailcheer. It must be copied in full, with no extra space or character.
  • The email field is missing from the delivery. Typeform only sends the questions the person actually answered. An optional email question, or one skipped by the form's logic, will not be there.
  • Typeform turned the webhook off. Typeform may deactivate a webhook that keeps running into errors, and it emails you when it does. Go back to Connect → Webhooks to check the address and the webhook's status.

Sources