Resources · Make integration

beehiiv Make integrationAutomate beehiiv with Make.

Can Make run the busywork around your newsletter? The beehiiv Make integration gives you 40 modules, including 8 triggers, to handle subscribers, segments, tags and automations. This guide connects your account, builds a first scenario and explains every module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the beehiiv Make integration automate?

The beehiiv Make integration links your newsletter to the rest of your tools. A scenario, the automation you build in Make, reacts when a reader subscribes, confirms, upgrades or leaves, then creates, tags, updates or enrolls subscribers in beehiiv without any code.

Paid readers onboarded on their own. Watch for Upgrades fires when someone moves to premium, and Add Subscriber to an Automation drops them into the welcome flow you designed for paying members.

A list fed by your other tools. A checkout, a webinar form or an event registration can call Create a Subscriber, then Add Tag to a Subscriber records where that reader came from, so segments stay meaningful.

Cleaner exits. Watch for Unsusbcribes and Watch for Downgrades tell your CRM or your support team right away, so nobody keeps writing to a reader who left.

What the module list does not do: there is no module to write, schedule or send a post, and no module to create a segment. For those gaps, Make an API Call reuses your connection to reach the beehiiv API. If you also look at n8n, the n8n vs Make comparison lays out the criteria. The Make training covers scenario design from scratch, and Make pricing explains how operations are counted.

Connect

How do you connect beehiiv to Make?

  1. 01

    Create an API key in beehiiv

    In beehiiv, open Settings at the bottom left, then API in the sidebar. Click Create New API Key and keep the value somewhere safe. beehiiv may first ask you to verify your identity through Stripe.

  2. 02

    Copy your Publication ID

    On that same API page, find the Publication ID section and copy the value listed under API V2. Make needs it to know which newsletter your modules work on.

  3. 03

    Paste both into Make

    Add any beehiiv module to a scenario and click Create a connection. Give it a name if you like, paste the key into API Key and the ID into Publication ID, then click Save. That connection, your beehiiv account linked to Make, serves every beehiiv module afterwards.

First scenario

Your first scenario: onboard new premium readers

GoalWhen a reader upgrades to premium in beehiiv, Make enrolls them in your paid-member automation.

  1. 01

    Start a scenario

    From the Scenarios page, create a new scenario and click the big +. Search for beehiiv and pick Watch for Upgrades, the instant trigger that listens for premium upgrades.

  2. 02

    Link the webhook and your account

    Click Create a webhook, then Create a connection and paste your API key and Publication ID. From now on, beehiiv calls Make every time a reader upgrades.

  3. 03

    Add the enrollment module

    Click the + on the right of the trigger and choose Add Subscriber to an Automation. Pick your paid-member flow, which must start with an active Add by API trigger in beehiiv, then map the upgraded subscriber from the trigger's bundle.

  4. 04

    Test, then switch it on

    Click Run once and trigger an upgrade with a test account. Read the bundle each module received. When the reader shows up in the flow, turn the scenario on so it keeps running.

Triggers

What can start a beehiiv scenario?

8 modules start a scenario when something happens in beehiiv. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by beehiiv as soon as it happens.

beehiiv1Watch for Subscribers

Watch for Subscribers

Instant trigger

In MakeTriggers when a new user subscribes and fires the scenario.

Every new sign-up to your newsletter starts the scenario, so a fresh reader can reach your CRM, a spreadsheet or a team channel without anyone copying an address by hand. Each subscriber arrives as one bundle, the item handed to the next module.

How it fires
instant, beehiiv calls Make through a webhook as soon as someone subscribes.
When to use it
every new reader should be logged or greeted somewhere outside beehiiv the moment they join.
Watch out
the webhook comes first, so click Create a webhook before Create a connection.
beehiiv2Watch for Subscription Confirmations

Watch for Subscription Confirmations

Instant trigger

In MakeTriggers when a users subscription is confirmed by completing the double opt-in and then fires the scenario.

Only readers who complete the double opt-in reach this trigger. You get a cleaner stream than raw sign-ups, since addresses that never clicked the confirmation email stay out of your other tools.

How it fires
instant, beehiiv calls Make through a webhook as soon as a subscription is confirmed.
When to use it
your sales or partner team should only see readers who proved their address is real.
Watch out
running it next to Watch for Subscribers toward the same destination can record one reader twice, so pick one of the two per destination.
beehiiv3Watch for Updates

Watch for Updates

triggerIn the docs only

This trigger sits in the Subscribers group of the Make documentation, but it comes without any description. Its name suggests changes to subscriber records, which is only a reading of the label, not a documented behavior.

How it fires
scheduled, Make checks beehiiv on the scenario's schedule, every 15 minutes by default.
When to use it
when none of the instant triggers covers the change you care about and you have confirmed what it returns.
Watch out
click Run once after editing a test subscriber and read the bundle before building anything on it.
beehiiv4Watch for Downgrades

Watch for Downgrades

Instant trigger

In MakeTriggers when a subscriber downgrades from a premium subscription and fires the scenario.

When a paying reader leaves premium and drops back to the free tier, this trigger lets you react instead of discovering it in a report. It is the signal for a retention email or a personal note.

How it fires
instant, beehiiv calls Make through a webhook as soon as the downgrade happens.
When to use it
whoever handles churn should hear about each lost premium reader and have a chance to ask why.
Watch out
it only covers premium downgrades; a reader who leaves the list entirely goes through Watch for Unsusbcribes.
beehiiv5Watch for Survey Form Submission

Watch for Survey Form Submission

Instant trigger

In MakeWatches for webhook submissions of survey forms.

Answers to your beehiiv survey forms reach Make as they are submitted, so feedback lands in a sheet, a CRM note or a team channel instead of staying inside the newsletter dashboard.

How it fires
instant, beehiiv calls Make through a webhook as soon as a form is submitted.
When to use it
a reader survey drives decisions and the answers should be read by people who never open beehiiv.
Watch out
the documentation does not describe how answers are structured, so submit a test response, click Run once and look at the bundle before mapping anything.
beehiiv6Watch for Post Sends

Watch for Post Sends

Instant trigger

In MakeTriggers when a post is published and fires the scenario.

Publishing a post becomes the starting point of a scenario. The new issue can be announced on social media, logged in an editorial sheet or shared with sponsors without a separate copy and paste.

How it fires
instant, beehiiv calls Make through a webhook as soon as a post is published.
When to use it
every issue should trigger the same follow-up tasks, whoever pressed the publish button.
Watch out
if the next modules need more about the post than the trigger passes on, add View a Post right after it.
beehiiv7Watch for Unsusbcribes

Watch for Unsusbcribes

Instant trigger

In MakeTriggers when a user unsubscribes and fires the scenario

The moment a reader leaves your list, Make knows. That lets you stop other tools from writing to someone who clearly said no, which protects your reputation as a sender.

How it fires
instant, beehiiv calls Make through a webhook as soon as someone unsubscribes.
When to use it
the same person also sits in a CRM sequence or a customer list that should be updated when they leave.
Watch out
the module name carries a typo in Make, so search for it by typing only the start of the word, and remember downgrades have their own trigger.
beehiiv8Watch for Upgrades

Watch for Upgrades

Instant trigger

In MakeTriggers when a subscriber upgrades to a Premium subscription and fires the scenario.

A reader switching to a premium subscription starts the scenario, which is the right time to welcome them properly, give access to a member space or alert the person who handles paid readers.

How it fires
instant, beehiiv calls Make through a webhook as soon as the upgrade happens.
When to use it
paying readers deserve an onboarding different from free ones, and it should start without manual follow-up.
Watch out
pairing it with Add Subscriber to an Automation requires a beehiiv flow that starts with an active Add by API trigger.
Modules

What can each beehiiv module do?

beehiiv gives you 32 modules in 10 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Subscribers

8 modules
beehiiv1

Create a Subscriber

Action

In MakeCreates a subscriber in your beehiiv account.

Adds a reader to your beehiiv publication straight from another tool: a checkout, a webinar form, a row in a sheet. The new subscriber lives in beehiiv from then on, with no CSV import in between.

When to use it
people sign up outside beehiiv and should reach your list without a manual export.
Watch out
if the address might already be on the list, run View a Subscriber (via Email) first so the scenario knows which case it faces.
beehiiv2

List All Subscribers

Search

In MakeReturns a full/filtered list of subscribers.

Pulls your subscribers into Make, the whole list or a filtered part, one bundle per reader. That is the base for syncing beehiiv with a spreadsheet or a CRM.

When to use it
a one-off sync or an audit of who is really on the list.
Watch out
an operation is one module run on one bundle, and Make counts it on your plan, so a big list processed by several modules adds up quickly.
beehiiv3

View a Subscriber (via SubscriptionID)

Action

In MakeLookup the details of a single subscriber using their beehiiv-generated subscriptionId

Fetches one subscriber when you already hold the subscription ID that beehiiv generated, often passed along by a trigger earlier in the same scenario. The reader's details come back in a single bundle.

When to use it
a trigger or a list handed you that ID and the next steps need the full picture.
Watch out
three View a Subscriber modules exist; this one only accepts the subscription ID, not an email.
beehiiv4

View a Subscriber (via Email)

Action

In MakeLookup the details of a single subscriber using their email address.

Finds a reader from an email address alone, which is usually the only identifier your other tools share with beehiiv. You learn whether the person is on your list and get their record.

When to use it
a form, a payment tool or a support inbox gives you an email, and you need the beehiiv subscriber behind it before updating or tagging.
Watch out
an email typed with a typo on one side will not match, so clean addresses upstream when you can.
beehiiv5

View a Subscriber (via Subscriber ID)

Action

In MakeLookup the details of a single subscriber using their beehiiv-generated subscriber_id

Looks a reader up through the subscriber ID, a second identifier beehiiv generates alongside the subscription ID. Same kind of result, reached with another key.

When to use it
the data you received carries a subscriber_id rather than a subscription ID.
Watch out
the two IDs look alike, so check which one your source sends before choosing between this module and the SubscriptionID version.
beehiiv6

Update a Subscriber

Action

In MakeUpdates custom fields and/or unsubscribes a subscriber

Changes an existing reader's custom fields, or unsubscribes them, from outside beehiiv. Your list then reflects what your billing tool or CRM already knows.

When to use it
a customer switches plans in your billing tool and the matching custom field in beehiiv should follow.
Watch out
it only writes to custom fields that already exist; create them once with Create a Custom Field before mapping data into them.
beehiiv7

Batch Update Subscribers

Action

In MakeUpdate multiple subscribers at once using an array of subscription_ids

Applies one change to many readers in a single step, from a list of subscription IDs, instead of calling Update a Subscriber once per person.

When to use it
right after List a Segment's Members, to adjust a whole group in one go.
Watch out
the module expects the IDs gathered in one list, while a search sends them as separate bundles; an aggregator, the Make tool that groups bundles, bridges the two.
beehiiv8

Delete a Subscriber

Action

In MakeDeletes a subscriber

Removes a reader from beehiiv entirely, which helps when a deletion request reaches you through another channel and the newsletter must follow.

When to use it
a privacy request lands in your support inbox and the person has to disappear from every list, beehiiv included.
Watch out
nothing brings the subscriber back from Make; if the goal is only to stop emails, unsubscribe them with Update a Subscriber instead.

Publications

2 modules
beehiiv9

List All Publications

Search

In MakeReturns a list of publications with their publication IDs.

Returns the publications on your beehiiv account, each with its publication ID. Since that ID is what the connection asks for, this module clears up which newsletter is which.

When to use it
you run several newsletters and a scenario has to handle more than one of them.
Watch out
the connection holds a single Publication ID, so a second newsletter most likely needs its own connection.
beehiiv10

View a Publication

Action

In MakeViews the details of a single publication.

Reads what beehiiv stores about one publication, so a report or a multi-newsletter scenario can label each result with the right newsletter.

When to use it
a scenario serves several newsletters and its output must say which one each line belongs to.
Watch out
it needs a publication ID; List All Publications gives you the correct value when you are unsure.

Posts

3 modules
beehiiv11

List All Posts

Search

In MakeReturns a list of posts for a particular publication.

Brings the posts of one publication into Make, one bundle per post, so you can build an archive page, an editorial sheet or a recap for sponsors.

When to use it
you want an overview of your published issues outside the beehiiv dashboard.
Watch out
a long back catalog means many bundles, and every module placed after this one runs once per post.
beehiiv12

View a Post

Action

In MakeView the details of a single post.

Fetches one post in detail when you already know which one you want, for instance the post that Watch for Post Sends just reported.

When to use it
a trigger told you an issue went out and the next module needs more about it than the trigger carried.
Watch out
it reads a single post; to scan several, start from List All Posts instead.
beehiiv13

Delete a Post

Action

In MakeDeletes (a draft) or archives (a published) a post.

Tidies up a post from a scenario, with a twist worth knowing: a draft gets deleted, while a published post is archived rather than erased.

When to use it
an editorial sheet marks a draft as dropped and beehiiv should reflect that decision.
Watch out
on a draft the deletion is final, so filter the scenario carefully before this module runs.

Segments

4 modules
beehiiv14

List All Segments

Search

In MakeReturn a list of segments from a publication.

Lists the segments of a publication, the saved groups of readers you defined in beehiiv. It is where you find the segment ID other modules ask for.

When to use it
before List a Segment's Members or View a Segment, to target the right group.
Watch out
segments are built inside beehiiv; this app has no module to create one from Make.
beehiiv15

List a Segment's Members

Search

In MakeReturns the members of a segment.

Returns the readers inside one segment, one bundle each, so a group such as your most engaged readers can be pushed into a CRM, an ads audience or a thank-you sequence.

When to use it
rewarding or re-engaging a precise group without exporting a CSV.
Watch out
a large segment produces many bundles, and each later module runs once per member.
beehiiv16

View a Segment

Action

In MakeLookup the details of a single segment using their beehiiv-generated segmentId

Reads one segment through the ID beehiiv generated for it, a quick way to confirm the segment still exists before acting on its members.

When to use it
as a check step at the start of a scenario that tags or updates a whole segment.
Watch out
you need the segment ID, which List All Segments shows you.
beehiiv17

Delete a Segment

Action

In MakeDeletes a particular segment.

Removes a segment from the publication, handy for clearing out temporary groups built for a single campaign once it has ended.

When to use it
your segment list is cluttered with one-shot groups nobody uses any more.
Watch out
like every Delete module, it cannot be reversed from Make, so double check the ID with View a Segment first.

Automations

5 modules
beehiiv18

Add Subscriber to an Automation

Action

In MakeAdd an existing subscription to an automation flow. Requires the automation to have an active Add by API trigger. The specified email or subscription_id will be matched against your existing subscribers. If an existing subscriber is found, they will be enrolled immediately.

Enrolls an existing subscriber in a beehiiv automation flow, matched by email or subscription ID, and the enrollment starts right away.

When to use it
something outside beehiiv, a purchase or a webinar attendance, should start a specific email journey.
Watch out
the automation needs an active Add by API trigger in beehiiv, and the person must already be a subscriber; create them first if not.
beehiiv19

List All Automations

Search

In MakeReturns a list of automations for a publication

Lists the automations of a publication, which gives you the IDs to feed into Add Subscriber to an Automation or View an Automation.

When to use it
while building, to find the flow you want a scenario to target.
Watch out
reading the list starts nothing; people only enter a flow through Add Subscriber to an Automation.
beehiiv20

List All Automation Journeys

Search

In MakeRetrieve all automation journeys associated with an automation that belongs to a specific publication. Optionally, you may filter by a user's subscription ID.

Retrieves the journeys tied to one automation, with an optional filter on a reader's subscription ID. It shows who went through a flow, or which journeys one reader has in it.

When to use it
support needs to answer why a reader received, or missed, part of an email sequence.
Watch out
without the subscription ID filter, every journey of the automation comes back, which can mean many bundles.
beehiiv21

View an Automation

Search

In MakeView the details of a specific automation within a publication

Reads one automation of a publication in detail, useful to make sure a flow exists before a scenario starts sending people into it.

When to use it
as a guard step placed before Add Subscriber to an Automation in a scenario you share with colleagues.
Watch out
Make classes it as a search, so its result travels as bundles and a filter can stop the scenario when nothing comes back.
beehiiv22

View an Automation Journey

Search

In MakeRetrieve a specific automation journey step associated with an automation that belongs to a publication.

Zooms in on a single journey of an automation, for the moments when one reader's path matters more than the whole list.

When to use it
you already spotted the journey through List All Automation Journeys and need its details for a precise answer.
Watch out
start from List All Automation Journeys, which tells you which journey to open.

Custom Fields

5 modules
beehiiv23

Create a Custom Field

Action

In MakeCreate a custom field on a publication, for use in subscriptions

Adds a custom field to a publication, so each subscriber can carry extra data such as a plan, a city or a signup source.

When to use it
a new scenario is about to write information beehiiv does not store yet.
Watch out
keep it out of scenarios that run for every reader; a field is created once, then filled through Update a Subscriber.
beehiiv24

List All Custom Fields

Search

In MakeRetrieve all custom fields belonging to a specific publication

Retrieves every custom field of a publication, a quick inventory before you map outside data into them.

When to use it
before building an Update a Subscriber step, to confirm the field you plan to fill really exists.
Watch out
it lists fields, not their values per reader; to read one person's data, use a View a Subscriber module.
beehiiv25

View a Custom Field

Search

In MakeView a specific custom field on a publication

Reads a single custom field of a publication on its own, without pulling the whole list of fields.

When to use it
a scenario must check how one field is set up before writing into it, for example after a colleague edited it.
Watch out
Make lists it among the searches, so plan for the case where no field comes back.
beehiiv26

Update a Custom Field

Action

In MakeUpdate a custom field on a publication

Edits an existing custom field of a publication instead of creating a new one, which keeps your subscriber data in one place.

When to use it
your data model changed and a field needs adjusting without starting over.
Watch out
other scenarios may map this field; run them once with Run once after the change to see they still behave.
beehiiv27

Delete a Custom Field

Action

In MakeDelete a custom field from a publication

Removes a custom field from a publication, for cleaning up fields left over from an old campaign or a test.

When to use it
a field no longer feeds any segment or scenario and only adds noise.
Watch out
the deletion cannot be reversed from Make; check the field with View a Custom Field and make sure no scenario still writes to it.

Tags

1 module
beehiiv28

Add Tag to a Subscriber

Action

In MakeAdds a tag to a subscriber.

Puts a tag on a subscriber, the lightest way to mark where a reader came from or what they did outside beehiiv.

When to use it
someone buys, attends an event or downloads a guide, and you want to segment on that later.
Watch out
this app offers no module to remove a tag, so agree on tag names before a scenario starts writing them.

Email Blasts

2 modules
beehiiv29

List All Email Blasts

Search

In MakeReturns a list of email blasts.

Lists your beehiiv email blasts, one bundle each, so they can be logged in a sheet or pulled into a report next to regular posts.

When to use it
you want a single place that tracks every email sent from beehiiv.
Watch out
for the details of one blast, chain View an Email Blast after this module rather than guessing from the list.
beehiiv30

View an Email Blast

Action

In MakeViews the details of a single email blast.

Reads a single email blast in detail, which is enough when a scenario only cares about one specific send.

When to use it
an approval log or a client report needs the details of one blast your team sent.
Watch out
it needs to know which blast to read; List All Email Blasts gives you the reference.

Referral Program

1 module
beehiiv31

View a Referral Program

Action

In MakeLists the milestones, rewards, and stats from a referral program.

Pulls the milestones, rewards and stats of your referral program into Make, so a dashboard or a team channel can show how referrals are doing without logging into beehiiv.

When to use it
your team reviews growth in a shared sheet and referrals belong in it.
Watch out
it only reads the program; changing rewards or milestones still happens in beehiiv.

Other

1 module
beehiiv32

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Reaches any endpoint of the beehiiv API with the connection you already set up, for everything the ready-made modules leave out.

When to use it
you need an action the module list does not offer, such as working with posts beyond reading or deleting them.
Watch out
you write the request yourself, so this is the most technical module of the app; check the endpoint in the beehiiv API documentation first.
Need help

Need help automating beehiiv with Make?

A person reads every message.

FAQ

beehiiv and Make: common questions

01Is the beehiiv Make integration free?
Yes. beehiiv is a standard app in Make, so it works on the Free plan, like the 3,000+ standard apps offered on every plan. The Free plan limits you to 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in credits, meaning operations, each month.
02What does it take to connect beehiiv to Make?
A beehiiv account, an API key and your Publication ID. Both values sit in beehiiv under Settings, then API. Create the key with Create New API Key, and copy the Publication ID listed under API V2. beehiiv may ask you to verify your identity with Stripe before it shows the key. In Make, click Create a connection on any beehiiv module, paste the two values and click Save. For an instant trigger, click Create a webhook first.
03Do beehiiv triggers in Make fire in real time?
Seven of the eight do. Watch for Subscribers, Subscription Confirmations, Downgrades, Upgrades, Unsusbcribes, Post Sends and Survey Form Submission are instant: beehiiv calls Make through a webhook as soon as the event happens. Watch for Updates is the exception. It is scheduled, so Make checks beehiiv on the scenario's schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan. Paid plans can go down to 1 minute.
04What if a beehiiv module is missing in Make?
Use Make an API Call. It reaches any endpoint of the beehiiv API with the connection you already created, so you keep the same API key and Publication ID. It is the route for anything the 40 modules skip, like creating a segment or going further with posts than reading or deleting them. The Make documentation lists no numeric limit for beehiiv, so plan usage around your Make plan rather than an app quota.
05Make or n8n for beehiiv: which one fits?
It depends on the criteria that matter to you, not on a winner. On Make, beehiiv comes with 40 ready-made modules, 7 instant triggers, a guided connection and Make an API Call for the rest, and it runs on every plan. n8n often has a node for the same apps, so check what it offers for beehiiv and compare which modules you need, where your other automations already live and how each tool counts usage.