Integrations
Send form submissions to Discord
Create a webhook in your Discord server, then add its URL to your form in Formward as a webhook of type Discord. Every processed submission is posted into that channel with the form name in bold and the fields listed underneath.
Formward also tells Discord to ignore every mention in the message, so a submission cannot ping @everyone in your server. Webhooks need the Professional plan.
Set it up
- In Discord, open Server Settings, go to Integrations and click Create Webhook.
- Choose the channel the webhook posts to, give it a name such as Formward, and click Copy Webhook URL.
- In Formward, open the form, go to its Settings tab and scroll to the Connections panel. Choose Webhooks.
- Pick Discord in the type menu, paste the URL and click Add webhook. Leave the signing secret empty: Discord does not check it.
- Click Test next to the webhook. A message reading "This is a test delivery from Formward" should appear in the channel.
- Send one real submission and check the delivery on the form's Webhooks settings tab.
What Formward sends to Discord
The Execute Webhook body for a three-field contact form:
json
{
"content": "**New submission to Contact form**\nname: Ada Lovelace\nemail: ada@\u200bexample.com\nmessage: Do you ship to Norway?\n",
"allowed_mentions": { "parse": [] }
}allowed_mentions with an empty parse list makes Discord resolve no mentions at all. On top of that, every @ in a value gets a zero-width space and markdown characters are escaped.
The message lists the first six fields; underscore control fields are left out. When AI summaries are on, the summary is added in italics.
Plan and limits
- Webhooks, including the chat formats, need the Professional plan or above. A form can have several webhooks, and each one gets every submission independently.
- Only submissions that finish processing are sent. Spam is never posted, and neither is a submission that is held because the form's notification address has not been confirmed yet.
- A delivery succeeds when the endpoint answers 2xx within 10 seconds. A timeout, an error status or a redirect counts as a failure and is retried up to three more times with increasing delays.
- Every attempt appears in the delivery log on the form's Webhooks settings tab, with the response code and a Replay button for workspace owners and admins.
Where the data goes
Discord is a US service, so posting submissions there sends a copy outside the EU. That transfer is yours to assess as controller.
Formward stores and processes the submission in the EU. Posting it to a chat tool is a second copy that you choose to make, and it then lives under that platform's storage and retention rules. Record the destination in your own records of processing, and keep forms that collect sensitive data away from chat channels: send those to your own endpoint with a generic webhook instead.
Your data-flow page lists every destination each of your forms uses right now.
Troubleshooting
- A long message fails with code 400
- Discord caps message content at 2,000 characters. A submission with a very long text field can exceed it, and Discord rejects the post. The submission is still stored in Formward; open it there, and consider capping that field's length in your form.
- Test shows "failed" right away
- The webhook was probably deleted in Discord, or the URL was copied incompletely. Copy it again from Server Settings, Integrations, and replace it in Formward.
- The test works but real submissions never arrive
- Open the submission in your inbox and check its status. Spam is never forwarded, and a submission stays held, and undelivered everywhere, while the form's notification address is unconfirmed. Confirm the address from the email Formward sent to it and new submissions flow through.
Other integrations
Connect Discord to your first form
Create a form, point your HTML at it and set up Discord in a few minutes. Submissions are stored and processed in the EU.