Collect community feedback in one channel
Feedback submissions post to a dedicated #feedback channel, where moderators can react and discuss without leaving Discord.
New submission on your "Feedback" form
Send a channel message to #feedback in Discord
One-directional. A submission triggers the action — nothing is written back into your form.
Community feedback scatters by default — some in DMs, some in the general channel, some in a form nobody opens twice. This flow puts every feedback submission into #feedback as a plain channel message, so the whole server reads the same list in the same order as it arrives.
Game studios and SaaS communities use it to let moderators react rather than reply. A pile of thumbs-up on one message is a rough vote, and the messages stay searchable long after the member who wrote them has gone quiet in the channel.
Setting it up
- 1
Publish the feedback form and decide first whether #feedback is public. That single choice determines which answers you are willing to map into the message.
- 2
In Zapier, point the New Submission trigger at the feedback form and connect the formformform account that owns it.
- 3
Add Discord's Send Channel Message action, then select the server and the #feedback channel.
- 4
Open the message with Overall Satisfaction so the channel can be scanned by tone before anyone reads a word of the body.
- 5
Map "What could we improve?" as the main body of the message — that is the answer moderators act on, and it deserves the most room.
- 6
Add "What did you like most?" underneath as a shorter line, so praise and criticism arrive together rather than as two separate posts.
- 7
Leave Email Address out of the message on a public channel. It stays in your formformform responses list, where only your team can search it.
- 8
Agree a reaction convention with your moderators before you switch the Zap on, then test with one submission and go live.
What maps where
Using the Customer Feedback Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Discord |
|---|---|
| Name | Message header, so members can be credited in the channel |
| Overall Satisfaction | First line, used as the scannable tone marker |
| What could we improve? | Main body of the channel message |
| What did you like most? | Shorter line beneath the improvement answer |
| Anything else you'd like to share? | Final line, omitted when the answer is empty |
Variations worth knowing
Point the Zap at a forum channel rather than a text channel. Every submission then opens a post of its own, so discussion about one idea stays under it instead of scrolling out of sight in a shared feed.
Filter in Zapier on the recommendation answer. Low scores route to a private channel where someone follows up by email, and everything else still posts to #feedback for the community to read and react to.
If something isn't arriving
Two Zaps are usually watching the same form after a duplicate was left running during testing. Open your Zap list, filter by the form name, and turn off all but one. Messages already posted have to be deleted in Discord by hand.
Questions nobody filled in come through empty, so Discord prints the label with nothing after it. Either mark those questions required in the form, or add a Zapier formatter step that drops empty values before the message is assembled.
Frequently asked questions
Should the submitter's email go into a public feedback channel?
Most servers leave it out. The address stays in your formformform responses list where only your team can see it, and the channel carries the feedback itself. Map it in only when #feedback is private and members expect that.
Can moderators reply to feedback from inside Discord?
They can reply in the channel or open a thread, and that discussion stays in Discord. Nothing travels back to formformform or to the person who submitted, because the connection runs one way — a reply is for the team, not the author.
How do I keep #feedback from filling with junk?
Filter in Zapier before the Discord step so only submissions that clear your rules post — a minimum length on the improvement answer works well. Everything else still lands in your responses list, where you can search and export it later.
Related automations
- Alert the team when a new order comes in
Each new order pings #orders with the product, quantity and buyer details, so fulfilment can start straight away.
- Drop new demo requests into your sales channel
Every demo request posts to #sales as a Discord message, so a rep can claim the lead in a thread while it is still warm.
- Post event RSVPs to your members
Each RSVP posts to #events as an embed, so organisers and members watch the guest list fill up as people sign up.
- Route job applications to a private hiring channel
Applications land in a private #hiring channel, where reviewers vote with reactions and discuss the candidate in a thread.
- Turn bug reports into support threads
Each bug report lands in #support as a Discord embed, so whoever is on shift can read it and start a thread on the spot.
- Alert the on-call team when a support ticket arrives
Each new ticket posts to #support with its subject and priority, and @here fires only when the priority justifies interrupting a shift.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free