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.
New submission on your Contact us form
Create or update the contact and add a note with the message body to their ActiveCampaign record
One-directional. A submission triggers the action — nothing is written back into your form.
A message sent through a contact form is context that disappears the moment it is answered from an inbox. Writing it onto the contact record as a note keeps the question, the date and the sender's name in one place the team already opens before replying to anybody.
Support and customer success teams use this when the same people write in repeatedly and the history behind a question matters more than any single reply does.
Setting it up
- 1
Publish your Contact us form in formformform with Full Name, Email Address, Subject and Message, and link it from the footer and your help pages.
- 2
In Zapier, choose formformform's New Submission trigger and select the contact form.
- 3
Add ActiveCampaign Create/Update Contact, so a returning sender updates the record you already hold rather than creating a second one.
- 4
Map Email Address to Email and Full Name to the name fields, splitting it with a Formatter step if your account expects first and last separately.
- 5
Add a second ActiveCampaign action, Create Note, with the note body set to Subject followed by Message so the record shows exactly what was asked.
- 6
Map Phone Number to the contact's phone field, so a reply by call does not need a second lookup somewhere else.
- 7
Add a tag such as inbound-question if you want a monthly count of how many people wrote in.
- 8
Test with a submission containing a deliberately long message and confirm the whole body is stored on the note.
What maps where
Using the Contact Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | ActiveCampaign |
|---|---|
| Full Name | Contact First Name and Last Name |
| Email Address | Contact Email, which matches the sender to an existing record |
| Phone Number | Contact Phone |
| Subject | First line of the note, so the record is scannable |
| Message | Body of the note on the ActiveCampaign contact |
Variations worth knowing
Run Zapier paths on the Subject answer and set a different ActiveCampaign contact owner in each: billing, technical, partnerships. The note still carries the message, and the owner field decides whose queue the person shows up in that morning.
Add a second action creating a ticket in whatever tool your team answers from, so the ActiveCampaign note is context rather than the queue itself. Both actions read the same submission and run independently, so neither one blocks the other.
If something isn't arriving
The note step is keyed on something other than the email address, so it cannot find the record the previous action just touched. Pass the contact ID out of Create/Update Contact and into the note action directly.
Add a Zapier filter on the Message field for the strings you keep seeing, plus a sanity check on Email Address. Nothing needs deleting in formformform — the responses stay recorded, they just stop moving forward into ActiveCampaign.
Frequently asked questions
Can the team reply from ActiveCampaign?
They can email the contact from ActiveCampaign, and the note gives them the original wording to reply to. The reply itself never returns to formformform, where the submission stays readable as the record of what was originally sent.
Should a contact form really create a marketing contact?
Create the record, but keep it off marketing lists until the person opts in. A contact in ActiveCampaign is only a record; subscription is separate. Tag these as inbound-question so a newsletter broadcast never reaches them by accident.
What happens to very long messages?
ActiveCampaign notes hold a lot of text, but Zapier will trim a value if you have mapped it into a shorter custom field. Map Message into the note body rather than a length-limited field, and test with your longest real example.
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.
- 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.
- 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