Skip to content

Send form submissions to a Discord channel

Post each form answer to a Discord channel as a tidy embed, with mentions switched off so nobody can ping your whole server.

2 min read

On this page

Discord is where many communities, game studios and small teams already talk all day. Sending form submissions there means applications, bug reports and orders show up where people will actually see them. Discord makes this easy with channel webhooks, and it takes about five minutes.

1. Create a webhook in Discord

  1. Open the server, hover the channel and open its settings with the gear icon.
  2. Go to Integrations, then Webhooks, and choose New Webhook.
  3. Give it a name and an avatar people will recognise, such as Website forms.
  4. Choose Copy Webhook URL. Keep it private: anyone with it can post to the channel.

2. Add Discord as a destination

In Formpik, open Destinations, add Discord and paste the address. Every flow in the workspace can then post to that channel.

3. Post from your flow

Open the flow of your form and add a Post to Discord step. Write the first line, such as New application from {{name}}, and pick the answers to include. Formpik sends them as an embed under that line, one field per answer, with short answers side by side and longer ones on their own row.

Safe by default

Visitors type whatever they like into your form. If their answer contains @everyone or a role mention, a careless integration would ping your whole server. Formpik switches mentions off on every Discord post, so the text shows as written and nobody gets notified by a stranger. Very long answers are shortened to fit Discord's limits instead of making the post fail.

Keep the channel useful

  • Send only what people act on. A Route by answer step can send bug reports to one channel and partnership requests to another.
  • Stop spam first. Put a Validate step before the post, and keep the spam trap on. Submissions caught as spam run no flows, so they never reach Discord.
  • Leave personal details out. A public or busy channel rarely needs an email address or a phone number. Include them in the email to the team instead.

Test it

Run the flow from the editor's test panel to check each step without posting, then send one test submission and watch it arrive in the channel. If the webhook was deleted in Discord, the run shows the step as failed with the reason, and you can run it again after adding a new address.

References

Keep reading

More from the blog