Set lifecycle stage on every newsletter signup
Subscribers become HubSpot contacts with a lifecycle stage and topic preferences already set for the nurture campaign.
New Submission on your "Subscribe" form
Create or update a contact and set lifecycle stage and marketing properties in HubSpot
One-directional. A submission triggers the action — nothing is written back into your form.
A subscribe form is usually three fields in a footer, which is why the list it builds so often arrives in HubSpot as bare email addresses with no stage and no topic attached. Setting both at the moment of signup is what makes that list usable later.
Content teams running an embedded subscribe block use this to keep segmentation honest. Someone who ticked two topics receives the campaigns for those two topics, and the lifecycle stage means the contact shows up in reporting rather than sitting outside the funnel entirely.
Setting it up
- 1
Embed the subscribe form where it belongs and publish it — the two-line embed drops into a footer, an inline block or a slide-in.
- 2
In HubSpot, create the topic property first, as a multiple checkboxes property whose options match the topic choices on your form word for word.
- 3
Set the Zap trigger to New Submission and select the subscribe form.
- 4
Add HubSpot Create or Update Contact, so a reader who resubscribes updates their record instead of creating a second one.
- 5
Map Email Address and First Name, then map Topics You're Interested In to the topic property you created.
- 6
Set lifecycle stage to Lead as a static value on the action rather than mapping it from a field — the form does not ask, and a blank value achieves nothing.
- 7
Decide what happens to existing customers who subscribe: HubSpot will not move a lifecycle stage backwards by default, so a customer who signs up stays a customer.
- 8
Subscribe with a test address, check the stage and topics on the new contact, then switch the Zap on.
What maps where
Using the Newsletter Signup Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | HubSpot |
|---|---|
| Email Address | Contact email — the property HubSpot matches on |
| First Name | Contact first name, used by the nurture emails |
| Topics You're Interested In | A multiple checkboxes contact property that drives active list membership |
Variations worth knowing
Once the topic property is populated, build an active list in HubSpot for each option. Membership updates itself as new subscribers arrive, so whoever writes a given newsletter always has the right audience without asking anyone to export a CSV.
Add a Zapier filter that inspects the domain of the submitted address. Business addresses can take a different lifecycle stage, or an extra property for sales to see; personal ones pass through as plain subscribers. Both still reach HubSpot.
If something isn't arriving
Multiple checkboxes properties expect separate values, not a comma-joined sentence. In Zapier, map the topic field so each selection is passed as its own line, and confirm the option labels in HubSpot match the form's wording exactly.
Sending a static Lead value on every submission can overwrite a stage that has moved on. Use HubSpot's setting that prevents lifecycle stages moving backwards, or add a filter so the stage is only set when the contact is new.
Frequently asked questions
Does unsubscribing in HubSpot remove the submission from the form?
No. The two are separate. HubSpot owns subscription status and unsubscribes, while formformform keeps the original submission as a record of the signup. Nothing is written back from HubSpot into the form, which is why your consent record stays intact.
Do I need a double opt-in step?
That is a HubSpot decision rather than a form one. Let the subscribe form create the contact, then have a HubSpot workflow send the confirmation and only add them to the sending list once they click. GDPR expectations vary by market.
Can I add a subscribe checkbox to a form that already goes to HubSpot?
Yes. Any form can carry a consent checkbox, and the same Zap can set the subscription property from it. Keep it a genuine opt-in — unticked by default, with wording of its own — rather than bundling consent into the submit button.
Related automations
- Add webinar registrants to a HubSpot workflow
Each webinar signup adds the contact to a HubSpot workflow and records which event they registered for.
- Create or update a contact from every demo request
Each demo request creates or updates a HubSpot contact with the requester's name, work email, company and phone.
- Log a support request as a note on the contact
Each support submission finds the customer in HubSpot and adds a timestamped note with the issue details.
- Log product feedback on the customer's record
Product feedback updates the HubSpot contact and logs a note, putting requests where account teams already look.
- Open a deal when a quote request arrives
Every quote request opens a deal in your chosen HubSpot pipeline and stage, associated with the person who asked.
- Add newsletter signups to Zoho CRM as tagged contacts
Every newsletter opt-in becomes a Zoho CRM contact carrying a tag you can build a campaign list from.
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