Open a deal in ActiveCampaign for every demo request
Every demo request creates or updates a contact and opens a deal in your ActiveCampaign pipeline, ready for a rep to work.
New submission on your Request a demo form
Create or update the contact and open a deal in your sales pipeline
One-directional. A submission triggers the action — nothing is written back into your form.
Demo requests are the one form where a delay costs money. This flow creates the contact and opens a deal in the same run, so the request shows up in ActiveCampaign CRM as work waiting to be picked up rather than an email somebody has to notice in a shared inbox.
Sales teams that already run their pipeline in ActiveCampaign use it to remove the retyping step between inbox and deal record, which is also where the qualification answers usually get lost.
Setting it up
- 1
Publish your Request a demo form in formformform with Work Email, Company and When are you looking to implement?, so a rep has qualification detail before the first call.
- 2
In Zapier, choose formformform's New Submission trigger and select the demo form.
- 3
Add ActiveCampaign Create/Update Contact as the first action and map First Name, Last Name, Work Email and Company, so the deal has a contact to attach to.
- 4
Add a second action, ActiveCampaign Create Deal, and pick the pipeline and the first stage your team actually works from rather than the default.
- 5
Build the deal title from Company plus the words 'demo request', so the pipeline board is readable without opening each card.
- 6
Set the deal owner to whoever handles inbound, or rotate owners with a Zapier path if inbound is shared across the team.
- 7
Map What problem are you trying to solve? into a deal note, so the rep reads the prospect's own wording inside the deal.
- 8
Run a test submission, confirm the deal lands in the right stage with the contact linked, 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 | ActiveCampaign |
|---|---|
| First Name | Contact First Name |
| Last Name | Contact Last Name |
| Work Email | Contact Email, and the record the new deal is attached to |
| Company | The contact's Organization field, and the first half of the deal title |
| When are you looking to implement? | Deal custom field for timeline, so the board can be sorted by urgency |
| What problem are you trying to solve? | Note on the deal, read before the first call |
Variations worth knowing
Add a Slack or email step after Create Deal so the owner sees the request within seconds. The deal is the record of the work; the notification is what makes someone open it the same morning rather than at the weekly review.
Filter on Company Size or on When are you looking to implement?, and create the deal only above your bar. Everything below it becomes a tagged contact in a nurture sequence, which keeps the pipeline an honest picture of live work.
If something isn't arriving
The Create Deal step is missing the contact ID from the previous action. Map that ID explicitly rather than relying on the email address alone, and confirm Create/Update Contact really is the first action in the Zap.
Stage IDs change when you rebuild a pipeline in ActiveCampaign. Reopen the Zap, reselect the pipeline and the stage from the dropdown instead of leaving the stored ID, and run one test before your next campaign goes out.
Frequently asked questions
Does the deal step need the contact created first?
Order the actions so Create/Update Contact runs first and pass its contact ID into the deal step. A deal with no linked contact is hard to work from, because the rep cannot see who asked or reply from the record.
How do I keep test submissions out of my pipeline?
Add a Zapier filter on the email domain and skip your own. While setting up, use the Zap editor's sample data rather than the live form, and delete any test deal in ActiveCampaign before you turn the Zap on.
What if the same person requests a demo twice?
The contact updates, but the deal step creates a second deal unless you add a search first. Use ActiveCampaign's Find Deal step and branch on the result, or accept duplicates and merge them at your weekly pipeline review.
Related automations
- Add webinar registrants to a list and tag the session
Registrations join your Event attendees list and pick up a session tag, so reminders and follow-up can run per event.
- Save contact form messages as notes on the contact
Contact form messages are saved as notes on the ActiveCampaign contact, giving your team the full question before replying.
- Subscribe newsletter signups to an ActiveCampaign list
Every newsletter signup becomes an ActiveCampaign contact and joins your Newsletter list the moment the form is submitted.
- Tag customers by their feedback score
A post-purchase score becomes a tag on the ActiveCampaign contact, splitting promoters from customers who need following up.
- Tag lead magnet downloads and start a nurture automation
Each gated download creates a tagged contact in ActiveCampaign and starts the nurture automation that matches their stated interest.
- Add buyers to a customers list after each order
Each order form submission adds the buyer to a Customers list in Constant Contact for updates and repeat-purchase emails.
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