Send one demo request to your CRM, sheet and Slack
A single demo request creates a CRM contact, adds a row to the reporting sheet and posts to the sales channel in one multi-step Zap.
New Submission on your Request a demo form
Run a multi-step Zap that creates a CRM contact, adds a row to your tracking sheet and sends a Slack alert
One-directional. A submission triggers the action — nothing is written back into your form.
A demo request usually needs to be in three places before anyone acts on it: the CRM, so the rep has a record; the tracking sheet, so the week's numbers are right; and the sales channel, so someone actually sees it. Doing that by hand means one of the three gets skipped.
This flow puts all three in one Zap, in order, off a single submission. Growth teams reach for it when demo volume has outgrown a shared inbox but has not yet earned a routing tool.
Setting it up
- 1
Publish your demo request form and make Work Email required. Every downstream step keys off it, and a blank address breaks all three actions at once.
- 2
In Zapier, create a Zap, choose formformform's New Submission trigger, connect your account and select the demo request form.
- 3
Pull in a real test submission so Zapier learns the field names. First Name, Company Size and the two free-text answers all need to appear in the sample.
- 4
Add the CRM action first: create or update a contact, with Work Email as the matching key so a repeat requester updates rather than duplicates.
- 5
Add the spreadsheet action second, appending one row with the submission time, Company, Company Size and the implementation timeline.
- 6
Add the Slack action last, posting to your sales channel with the company name in the message heading and the problem description in the body.
- 7
Keep that order. The alert fires only once the record exists, so a rep clicking through from Slack finds something in the CRM rather than an empty search.
- 8
Test the whole Zap on one submission, check all three destinations agree, then switch it 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 | Zapier |
|---|---|
| Work Email | Contact email on the CRM record, and the matching key that prevents duplicates |
| First Name | Given name on the CRM contact and the greeting in the Slack alert |
| Company | Account name in the CRM, the company column of the tracking sheet, and the Slack heading |
| Company Size | Segment field on the CRM record and the column the weekly report groups by |
| What problem are you trying to solve? | Body of the Slack post, so the rep reads the context before replying |
| When are you looking to implement? | Timeline column in the tracking sheet |
Variations worth knowing
Move the Slack step onto a Path that reads Company Size. Large companies post to the sales channel, everything else to a quieter review channel. Keep the CRM and sheet steps ahead of the split so every request is recorded whichever way it goes.
Insert a Delay For step after the Slack post and a second message four hours later repeating the company name. If the first alert scrolled past during a busy morning, the reminder puts the request back in front of the channel while the day is still useful.
If something isn't arriving
The CRM step is set to create rather than create-or-update. Switch it to the find-or-create action and set Work Email as the search field, so a second request from the same person updates the existing contact instead of adding one.
The spreadsheet step is mapping fields that were empty in your test submission, so Zapier never learned them. Send a fresh test with every question answered, remap the columns from that sample, and re-run the step.
Frequently asked questions
Does the Zap stop if one of the three steps fails?
Yes. A multi-step Zap runs in order and halts at the step that errored, so later actions never run. Zapier keeps the failed run in your task history, and you can replay it once the CRM or Slack connection is fixed.
Can the rep's CRM notes show up on the form response?
No. The connection runs one way. A submission starts the Zap, and nothing the CRM or Slack produces is written back into formformform. The stored response stays exactly as the person submitted it, and the CRM record is where notes belong.
How many actions can one Zap have?
That depends on your Zapier plan rather than on the form. The trigger side is the same either way: one submission, one Zap run. If you need more steps than your plan allows, split the work across two Zaps watching the same form.
Related automations
- Let only qualifying applications reach the hiring manager
A Filter step checks location and hours first, so only qualifying applications create a candidate record and reach the hiring manager.
- Log every feedback score, then follow up a day later
Formatter cleans the rating into a number, the row lands in your analysis sheet, and a Delay sends the follow-up email a day later.
- Put each RSVP on the calendar and on the reminder list
Guests who say yes get a calendar invite and a place on the reminder list from the same Zap, with no spreadsheet export in between.
- Split urgent support requests into their own queue
A Path reads the priority answer and raises an escalated help desk ticket for urgent submissions, a standard one for everything else.
- Turn each order into an invoice and a confirmation email
Each order submission drafts an invoice in your billing app and sends the buyer a confirmation, so fulfilment and accounts stay level.
- Confirm event sign-ups and log the attendee
A registration becomes a calendar entry, a confirmation email and an attendee row, all from one scenario run.
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