Notifications · via Zapier

Connect Zunoform to Microsoft Teams 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 Microsoft Teams 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.

Posts each submission into a Teams channel so the people who act on a form see it where they already work.

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

Notify an operations channel about a new request

An internal request form can give a Teams channel the essentials: what is needed, when and who is coordinating it. Keep the message concise and leave detailed or sensitive information in the response system your team is authorized to use.

Prepare your Microsoft Teams account

Confirm your Microsoft 365 organization allows the Zapier connection and select an accessible team and channel. Test with the account that will own the integration, not just a temporary administrator account.

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 Microsoft Teams

Add an action step and choose Microsoft Teams. Connect your account, then pick the action that sends a message to a channel or a chat. 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.

Request summary: Destination: Message heading or body; Lead with the action the team needs to consider.
Requested date: Destination: Message body; Present it as a requested date, not a confirmed commitment.
Coordinator name: Destination: Message body; A name in text does not automatically create a Teams mention.
Fixed team and channel: Destination: Destination; Check visibility with an ordinary team member.

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 Microsoft Teams 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

Send a sample and inspect it in desktop and mobile Teams. Confirm line breaks, links and channel visibility, and ensure no unnecessary personal details are included.

If the result is missing or wrong

If authorization succeeds but delivery fails, inspect tenant policy and channel access. For webhook alternatives, consult current Microsoft guidance rather than relying on a retired connector setup.

Check the current Microsoft Teams 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

Do I need admin permission for this?

Possibly. Many Microsoft 365 tenants restrict which third-party apps may connect, so authorizing Zapier's Teams connection can require an administrator to approve it. Worth checking before you build the rest of the Zap.

Is there a native Teams integration?

No. Slack is our native notification integration on the Pro plan; Teams can be reached through Zapier. If you prefer a Microsoft workflow or webhook route, check current Microsoft support and provide the required message transformation; a raw response payload is not automatically a Teams message.

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.