Customer support · via Zapier

Connect Zunoform to Intercom via Zapier

This is not a one-click native integration. Zunoform posts every completed response to a Zapier catch hook, and your Zap does the rest — so there is no Intercom button inside Zunoform and no OAuth connection between the two products. What you get instead is a webhook connection with field mapping you control in Zapier.

Creates or updates an Intercom contact from each response, so what someone told you in a form is visible next to their conversation history.

Start free — no card See native integrations

The Zapier integration is on Zunoform’s free plan — 500 responses a month, no card. Webhooks by Zapier requires a paid Zapier plan; destination account requirements and task limits also apply.

Example workflow

Add onboarding context to a contact record

An onboarding questionnaire can tell your support team which workflow a customer wants to improve. Store a small set of useful attributes next to the contact, and keep detailed answers in a note or other supported destination rather than overloading every profile field.

Prepare your Intercom account

Decide how the Zap will find an existing contact and what it should do when none exists. Define custom attributes in Intercom first and confirm that the selected action exposes them.

Four steps, start to finish

Start with a published Zunoform form, a Zapier plan that includes webhooks, and access to the destination account. Some destinations require additional permissions or setup.

Create a Zap with a Catch Hook trigger

In Zapier, create a new Zap and choose Webhooks by Zapier as the trigger app, then Catch Hook as the event. Zapier generates a URL for you and shows it on the next screen. Copy it.

Paste the URL on the Zapier card in Zunoform

Open your form in the Zunoform builder, go to the Integrations tab, and paste the URL on the Zapier card. We only accept an https address on zapier.com, so a typo is rejected rather than silently failing later.

Submit a test response so Zapier learns the shape

Publish the form and fill it in once yourself. Zapier's trigger step will pick that submission up as sample data — without it, the field list in the next step is empty and there is nothing to map.

Map your fields to Intercom

Add an action step and choose Intercom. Connect your account, then pick the action that creates or updates a contact, or starts a conversation. Zapier's action list changes over time, so choose from what it shows you rather than hunting for an exact name. Drag your form's answers into the fields, test the Zap, and turn it on.

Suggested field mapping

Use this example to plan your form. Select the actual fields from your captured test response and the action available in your account; these are mapping suggestions, not a preconfigured Zap.

Email or your existing customer identifier: Destination: Contact lookup; Use the same identity convention as your application.
Team size: Destination: Configured attribute; Map a band to text, not a numeric field.
Primary use case: Destination: Configured attribute or note; Preserve the answer without claiming it is verified account data.
Onboarding comments: Destination: Supported note or text field; Avoid overwriting an unrelated attribute containing valuable history.

What Zapier receives

The payload includes formId, formName, responseId, submittedAt, status, answers and metadata. Answers are keyed by field ID, not by question label; inspect a test response to identify the answer you want. Multi-part answers can contain nested values, and uploads contain file references rather than binary attachments. Replacing a question can change its ID, so retest mappings after editing the form.

Delivery uses a background queue with retries for failed webhook requests. A successful hook does not confirm the later Intercom action succeeded. Check Zap history, and use responseId in a lookup or a processed-response log when duplicate processing would matter. Earlier responses are not automatically replayed when you connect the hook.

Test before sharing your form

Use a known test contact, then a new address. Confirm that the first is updated without duplication and the second follows your intended create-or-review path.

If the result is missing or wrong

If an update clears existing data, inspect mappings for unanswered optional questions. Add conditional handling rather than sending empty values into every contact attribute.

Check the current Intercom actions in Zapier and Zapier’s webhook setup and plan requirements before configuring your account. Action availability and permissions depend on your connected account.

Questions people ask

Will this match an existing Intercom contact?

If you map the email address and choose an action that updates rather than only creates, yes. Collect email in the form and use it as the matching key, or you will accumulate duplicate contacts.

Can form answers become custom attributes?

Yes, provided the custom attributes already exist in Intercom. Create them there first, then map answers to them in the Zap.

Is this a native Zunoform integration?

No. Zunoform sends each completed response to your Zapier catch hook; you configure the destination and field mapping in Zapier. The Zunoform connection is included on Free, but Webhooks by Zapier requires a paid Zapier plan. Native options include Google Sheets and Zoho CRM on Free, with Slack, Notion, HubSpot, Mailchimp, Airtable and Excel on Pro. Form notification emails on Free require your own SMTP configuration; platform-sent form emails require Pro or Business.