Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
Point a Discord channel webhook at your FormBridge form so every submission — a signup, a support ticket, an application — posts straight into the server your community already checks.
Get an instant summary, key takeaways, action items, and answers to your questions about this article.
In Discord, create a webhook for the target channel from Channel Settings → Integrations → Webhooks, copy the webhook URL, and paste it into your form's Slack & Discord notification field in FormBridge (Pro plan and above). Every new submission then posts as a message in that channel.
If your community, team, or side project runs on Discord, waiting on email to check form submissions is friction you don't need. A webhook gets each submission posted straight into a channel members already have open.
Inside your Discord server:
That's the whole setup on Discord's side — no bot to code, no OAuth flow, no permission scopes beyond the ability to post in that one channel.
Open the form in your FormBridge dashboard and go to its Slack & Discord notification settings. Paste the Discord webhook URL into the field and save. FormBridge posts a formatted message for each new submission, pulling in whatever fields the form collected — since FormBridge accepts any input name without a required prefix, there's nothing extra to configure to get a field showing up.
This is available on the Pro plan ($9/mo) and above; it's not part of the Free tier.
Submit the form, or send a quick test:
curl -X POST https://app.formbridge.ai/api/forms/fb_8h2k9p \
-d "full-name=Test User" \
-d "email=test@example.com" \
-d "message=Testing Discord notifications"
Check the connected channel for the message. If nothing arrives, verify the webhook wasn't deleted from Discord's side — removing a webhook invalidates the URL immediately, and FormBridge has no way to detect that until the next submission fails to post.
Email notifications still land in your FormBridge inbox and can run at the same time as Discord — nothing forces a choice. The advantage of Discord specifically is visibility for a distributed team or community: a submission becomes a message people see in passing, rather than something buried three unread emails deep. For a support form, feedback form, or a community application form tied to a Discord server, that immediacy is often the entire point of adding the integration.
No. Discord webhooks post messages directly to a channel without a bot, permissions setup, or server-wide app installation — it's a single URL you generate from the channel's settings.
No. Slack and Discord notifications are a Pro-plan-and-above feature on FormBridge; the Free plan covers email notifications and autoresponders only.
Each form's chat notification setting is one webhook URL, so it's set up for whichever platform you paste in — Slack or Discord, not simultaneously through the same field.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.