If your team already uses Discord, routing new form submissions there is a natural fit. A message in a dedicated channel is harder to miss than an email buried in a shared inbox, and the whole team sees it at once. This guide shows how to set up Discord alerts for new form submissions — without creating webhooks or exposing secrets in the browser.

Why you must not put a webhook URL in your page

Some tutorials POST form data straight to a Discord webhook from JavaScript. The webhook URL is the credential — anyone who copies it from your page source or network tab can spam your channel indefinitely.

Webhook URLs and bot tokens belong on a server, never in frontend code. With MyFormConnect, you connect your Discord server once in the dashboard and pick a channel per form. Our platform bot posts submission alerts server-side after each clean submission — your HTML never contains a webhook URL.

How the safe pattern works

Your HTML form posts to a MyFormConnect endpoint. The endpoint stores the submission, runs spam checks, and — when Discord is enabled for that form — sends an embed to the channel you selected. You can route different forms to different channels (leads, support, community questions) without touching your site code again.

Step 1: Connect Discord on desktop

Discord linking uses OAuth in the dashboard. Open MyFormConnect on a desktop browser (the connect flow is easiest there), then:

Go to your team's Integrations page
Open Discord and click Connect Discord
Choose the Discord server where alerts should land and authorize the MyFormConnect bot
Optionally pick a channel and click Send test message to confirm posts appear

No manual webhook setup and no bot token to copy. The bot needs permission to view channels and send messages in the channels you pick.

Step 2: Enable notifications on your form

Create a form in MyFormConnect (or open an existing one)
Open the form's Integrations → Discord panel
Turn on Enable Discord notifications
Select the target channel from the dropdown (for example #leads or #support) and save
Copy the form endpoint URL for your HTML form

Each form can post to a different channel — useful when sales leads and support questions should not share the same feed.

Step 3: Add the form to your page

<form action="https://myformconnect.io/f/YOUR_FORM_UUID" method="POST">

  <label for="name">Name</label>
  <input id="name" name="name" type="text" required />

  <label for="email">Email address</label>
  <input id="email" name="email" type="email" required />

  <label for="message">Message</label>
  <textarea id="message" name="message" rows="5" required></textarea>

  <!-- Identify which form/page this submission came from -->
  <input type="hidden" name="page_source" value="Contact page" />

  <button type="submit">Send message</button>

</form>

Set Redirect URL in form settings for a normal POST. With Ajax/fetch, handle success navigation in your own JavaScript.

Use case: support questions and community discussion

Discord works well when you want visitors to ask a question on your site and your team (or community) to pick it up in Discord — without exposing a public support email or managing tickets in a separate tool.

Create a form with fields like name, email, and question (or topic + details)
Route Discord notifications to a channel such as #support or #community-help
Set the form's Redirect URL to a thank-you page that invites them to join your Discord server — for example: "Thanks — we received your question. Join our community on Discord to follow the thread and help others with similar questions."
Include your Discord invite link on that thank-you page (and optionally in the redirect URL query string if you track campaigns)

Your team sees the full submission in Discord immediately and can reply there. Community members in the server can discuss and help each other on ongoing topics, while MyFormConnect keeps the original submission in your dashboard as the record of what was asked.

For a lighter-touch variant, post to a staff-only channel first and use the thank-you page purely as the community onboarding step — the form captures the question; Discord is where the conversation continues.

What the Discord alert looks like

Each new clean (non-spam) submission triggers an embed in your chosen channel. A typical alert looks like:

📬 New submission — Contact form

Contact form: Contact form
────────────────────────
Name          Email
Jan de Vries  [email protected]

Message
Interested in your enterprise plan — can we set up a call?

Open submission
View in dashboard

Submitted 27 Jul 2026 at 14:45 • #12345

The title follows your form template (for example "Contact form" or "New submission"). Standard fields like name and email appear first; other form fields follow. A link opens the full submission in your MyFormConnect dashboard.

Keeping the channel clean

Enable spam protection on your form — Discord alerts for spam submissions are noisy and unhelpful; only clean submissions are sent to Discord
Route high-volume forms to dedicated channels (for example #leads vs #support) or use a page_source hidden field to distinguish messages in the embed
Disable Discord notifications on forms you take offline — old indexed pages can still submit to a live endpoint

Keeping the team in the loop

Discord alerts work best alongside email notifications, not instead of them. Use Discord for real-time awareness — someone on the team sees the message and can respond quickly. Use email as the durable record. Both notifications come from the same submission; the endpoint handles both in parallel.

Enable spam filtering before you connect Discord. A single spam wave can flood a channel with tens of messages in a few minutes, which quickly trains your team to ignore the notification channel entirely.

Ready to collect form submissions?

Create a free MyFormConnect form endpoint and skip building your own backend.

Start Free Trial

No credit card required · 5-minute setup

How to Send a Discord Alert for a New Form Submission