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.
New submission on your "Request a demo" form
Send a channel message to #sales in Discord
One-directional. A submission triggers the action — nothing is written back into your form.
A demo request is worth roughly as much as the speed of the reply. This flow takes each submission from your demo form and posts it as a message in #sales, with the name, company and work email already laid out, so nobody has to go digging through a shared inbox first.
Sales teams that run their day in Discord reach for this one first. A rep claims the lead in a reply thread, and the thread becomes the record of who picked it up and what happened next. The form stays the only place a prospect enters anything; Discord just receives it.
Setting it up
- 1
Publish your demo request form. The Demo Request Form template already asks for First Name, Last Name, Work Email and Company, which is most of what a rep needs before the first call.
- 2
In Zapier, point formformform's New Submission trigger at that demo form specifically, so #sales never picks up newsletter or support traffic from another form.
- 3
Add Discord's Send Channel Message action, connect the account that has access to your server, and select #sales as the destination channel.
- 4
Open the message with First Name and Last Name, then put Company and Job Title on the second line — that pair is what tells a rep whether the lead is theirs to claim.
- 5
Put Work Email and Phone Number on their own separate lines underneath, so a rep can copy one without picking it out of a sentence.
- 6
Add "What problem are you trying to solve?" as the closing block — that answer usually decides which rep takes the lead.
- 7
Decide on mentions. Ping a sales role on every message only if #sales is genuinely quiet; otherwise leave it silent and let the channel be the queue.
- 8
Send one test submission through the live form, check how it renders in #sales, then switch the Zap on.
What maps where
Using the Demo Request Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | Discord |
|---|---|
| First Name | Opening line of the Discord message, before the surname |
| Last Name | Opening line of the Discord message, after the first name |
| Company | Second line, next to the job title |
| Job Title | Second line, so reps can judge seniority at a glance |
| Work Email | Its own line, kept clean so it can be copied in one go |
| Phone Number | The line below the email, for reps who would rather call than write |
| What problem are you trying to solve? | Closing block of the message |
Variations worth knowing
Add a Zapier filter or paths step on the Company Size answer. Larger requests post to #sales with a role mention, and everything smaller drops into a #self-serve channel without one, so the busy channel keeps the attention it deserves.
Swap Send Channel Message for Send Channel Message in Embed if your reps prefer a card. The name becomes the embed title, company and job title sit as short fields, and the problem statement fills the description block.
If something isn't arriving
Zapier remembers field names from the sample submission you built the Zap with. If a question was renamed in the form afterwards, reload the sample in the trigger step, remap the affected lines, and run one more test before turning it back on.
Check the bot can post in that specific channel — a server-wide role is not enough when the channel has its own permission overrides. Then confirm the Zap is switched on and watching the demo form rather than a duplicate draft form.
Frequently asked questions
Can I send demo requests to more than one Discord channel?
Yes. Add a second Discord action to the same Zap and point it at another channel — one message to #sales and a quieter copy to a #lead-log, for instance. Both fire from the same submission, so the two channels never drift apart.
Does the Discord message update if the prospect submits the form again?
No. Each submission posts its own message, and nothing is written back into the form or edited after the fact. A second submission from the same person arrives as a new message, so treat the most recent one as current.
How quickly does a lead reach the channel?
The New Submission trigger is real time, so the message normally appears within seconds of someone pressing submit. Any delay you notice comes from Zapier's own task queue rather than the form, and a busy account can add a short wait at peak times.
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.
- Collect community feedback in one channel
Feedback submissions post to a dedicated #feedback channel, where moderators can react and discuss without leaving Discord.
- 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