What if a form does not have a first-name field?

Then no name is sent. Email is the only required field; anything else present is mapped, and anything missing is left blank in beehiiv.

Can I send different forms into different beehiiv welcome sequences?

Yes, on the beehiiv side. Every subscription this flow creates carries the form name in utm_source and in the signup_form custom field, so you can build a segment per form and attach an automation to each segment.

Does it run on Zapier as well?

A Zapier version is included. It drops the lookup step, because beehiiv keeps one subscription per address and will not create a second, but it also cannot tell you whether the address was new. Use the n8n version if that distinction matters to you.

What happens if beehiiv is down or the API key expires?

The execution fails and shows in n8n's execution list with the submission payload attached. Webflow keeps every submission in its own Forms tab, so nothing is lost; retry the execution from n8n once the key is fixed.

WfbhMade to order

Marketing & content publishing

Webflow form submission → beehiiv subscriber, tagged by form

Every site form feeds the newsletter, tagged with the form that captured it.

Webflow's native forms collect email addresses but have no route into beehiiv. This flow listens for each submission, checks whether the address is already subscribed, and creates the subscription with the form name as its source. Welcome emails go to new subscribers only. One list, with every signup traceable to the form that captured it.

How it works

Wf
Trigger
Form submission on any form in the site (form_submission webhook)
Webflow
if
Step 1
Normalise the submission
Email, first name, the form name and any hidden UTM fields are read from the payload, whatever the form's field labels are. The email is trimmed and lower-cased.
bh
Step 2
Look up the email in beehiiv
beehiiv's subscriptions-by-email endpoint returns the address's current status (active, pending or inactive), or a 404 when it has never subscribed.
if
Step 3
Skip active and pending subscribers
Active and pending subscribers stop here, which is what prevents a second welcome email. New and inactive addresses continue.
bh
Step 4
Create the subscription
A POST creates the subscription with utm_source set to the form name, utm_medium to website, referring_site to your domain, the signup_form custom field filled, send_welcome_email on, and reactivate_existing on so inactive addresses come back.

What changes once it runs

The subscriber appears in beehiiv within a minute of the form being submitted, with the welcome email on its way.
Each signup carries the form name in utm_source and in a signup_form custom field, so the subscriber record shows which form on the site captured it.
Existing subscribers are left alone: no second welcome email, no status change.
One workflow covers every form on the site. Add a form in Webflow and it is included from the next publish.

What you get

The n8n workflow export with the Webflow trigger and both beehiiv calls pre-built
Zapier: the same flow rebuilt as a Zap, minus the lookup step
Field-mapping sheet: which Webflow field names go to which beehiiv fields and UTMs
Setup guide covering the beehiiv API key, publication ID, custom field and the Webflow webhook
Recorded walkthrough of a test submission arriving in beehiiv

Before you start

A Webflow site with at least one native form, and a site API token allowed to read forms and create webhooks
beehiiv publication on a plan with API access (Scale or above)
A beehiiv API key and your publication ID, both from the Integrations page in Settings
A custom field named signup_form created in beehiiv before the first run
An n8n instance reachable from the internet, so Webflow can call the webhook

Built for

Questions before you buy

What if a form does not have a first-name field?: Then no name is sent. Email is the only required field; anything else present is mapped, and anything missing is left blank in beehiiv.
Can I send different forms into different beehiiv welcome sequences?: Yes, on the beehiiv side. Every subscription this flow creates carries the form name in utm_source and in the signup_form custom field, so you can build a segment per form and attach an automation to each segment.
Does it run on Zapier as well?: A Zapier version is included. It drops the lookup step, because beehiiv keeps one subscription per address and will not create a second, but it also cannot tell you whether the address was new. Use the n8n version if that distinction matters to you.
What happens if beehiiv is down or the API key expires?: The execution fails and shows in n8n's execution list with the submission payload attached. Webflow keeps every submission in its own Forms tab, so nothing is lost; retry the execution from n8n once the key is fixed.

Nearby on the shelf

Whole catalog