Discord
The Discord integration posts a message to a channel every time your form receives a response; ideal for community servers, events, and signups. It's free and needs no account connection: you paste a Discord channel webhook URL, and Floov posts to it.
Create a webhook in Discord
- In Discord, open Server Settings > Integrations > Webhooks (you need Manage Webhooks permission on the server)
- Click New Webhook, choose the channel it should post to, and optionally rename it
- Click Copy Webhook URL
Set it up on your form
- In the form editor, open Settings > Integrations > Discord
- Paste the webhook URL
- That's it; a valid URL turns delivery on. Publish the form to apply.
What the message looks like
Each response is posted as an embed with the form name (linked to the response in Floov), every submitted answer as label/value fields, and a submission number. Very long forms are trimmed to fit Discord's message size; the full response is always available in Floov.
Notes
- Delivery happens in the background after each submission. If it fails (for example the webhook was deleted in Discord), the response is still saved in Floov and the failure is logged; it never blocks the submission.
- A webhook posts to the one channel it was created for. To post to another channel, create a second webhook there and use its URL on that form.
- The webhook URL contains a secret; treat it like a password. Anyone with it can post to your channel. If it leaks, delete the webhook in Discord and paste a new URL.
- Leave the URL blank to turn Discord delivery off.
Checking delivery status
The form’s Deliveries page (from the editor menu) logs every submission’s delivery to each destination; webhook, Google Sheets, Slack, Discord, and email; with its status and the error for anything that failed, for the last 30 days.
Related
Prefer Slack? See Slack. To push data to your own endpoint, use webhooks. Browse collected data under Viewing responses.
For an already published form, you can also close this integration panel and choose Apply to live form at the top of the Integrations tab. This updates integrations and tracking without publishing other draft changes. New questions and hidden fields must be published before mapping them. See Publishing Forms.