Notifications · via Zapier

Connect Zunoform to Discord 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 Discord 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 response as a message in the Discord channel you choose, which is how most communities handle applications and reports.

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.

Discord expects a message payload in its own format. Zunoform sends a response payload, so a direct URL alone is not enough: use Zapier to map the message, or a separate service you control to transform the webhook before sending it to Discord.

Example workflow

Send moderator applications to a private review channel

A community application can collect experience, availability and a short explanation of why someone wants to help. Send a compact summary to the moderation team, keeping personal contact information out of public channels.

Prepare your Discord account

Choose a channel the connected Discord account or bot can access. Decide how much of the application belongs in a message; a long submission is usually better summarized than pasted in full.

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 Discord

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

Display name: Destination: Message heading; Use the provided name as text, not an automatically trusted Discord identity.
Availability and experience: Destination: Message body; Label both answers so reviewers can scan the application.
Response ID: Destination: Message reference; Include it to distinguish repeat applications.
Fixed private channel: Destination: Destination channel; Do not allow applicants to choose the destination.

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 Discord 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

Submit a long answer containing an @ mention and a link. Check readability and mention behavior in a test channel before using the moderator channel.

If the result is missing or wrong

If sending fails, check channel permissions and message length in the failed action. A Discord webhook expects a Discord-shaped message; posting the raw Zunoform response payload directly is not an equivalent setup.

Check the current Discord 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

Can I post to a private channel?

Yes, as long as the Discord account or bot you authorize in Zapier can see it. Server permissions apply exactly as they would for a human posting.

Should I use Zapier or a plain webhook for Discord?

Use Zapier when you want to configure the message with action fields. A custom webhook route can avoid Zapier, but you must provide a service that transforms the Zunoform response into Discord's message format and handles delivery.

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.