beehiiv

Grow and manage a beehiiv newsletter from your flows. Agents create and update subscribers with UTM attribution, adjust tiers and custom fields, enroll readers into automation journeys, and pull publications, posts, and segments for reporting.

12 actions API key available

beehiiv website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A new lead lands from the website form or a partner co-registration feed

List Subscriptions checks by exact email whether the reader already exists and in what status

Previously unsubscribed readers are held for review instead of being quietly reactivated

The growth owner reviews the held reactivations, because re-adding someone who opted out is a trust decision, not a data operation

Create Subscription adds the approved readers with UTM attribution, custom field values, and the welcome email

Enroll In Automation drops each new subscriber into the welcome journey through its active Add by API trigger

The day's subscriber counts by source post to the growth channel

What This Integration Enables

A newsletter's asset is not the content, it is the list, and lists rot at the edges: leads that never get imported, attribution that never gets recorded, tiers that no longer match reality. beehiiv's API makes the subscriber record fully operable, and FlowRunner agents work it continuously, feeding new readers in from every source with attribution intact, keeping tiers and custom fields synced to the systems that know the truth, and enrolling the right readers into the right journeys. The one operation that erases a reader entirely stays behind a human gate. - Sync leads from forms, CRMs, and spreadsheets into the publication as they arrive - Record UTM attribution and referring site at creation, not as an afterthought - Keep tiers and custom fields current as reader status changes in billing or the CRM - Enroll existing subscribers into automations with active Add by API triggers - Pull publications, posts, and segments into reporting and downstream tools

Without FlowRunner

Leads pool outside the list Signups from forms, partners, and spreadsheets wait for the weekly CSV import that sometimes happens

Attribution lost at the door Imported subscribers carry no UTM data, so growth reporting is a guess about which channels work

Profiles go stale A reader upgrades, churns, or changes segment elsewhere, and the newsletter profile never hears about it

With FlowRunner

Every source feeds the list in minutes New readers arrive with the welcome email sent and the journey started the same hour they signed up

Attribution recorded on arrival UTM source, medium, campaign, and referring site land on the subscription the moment it is created

Profiles maintained continuously Tiers and custom fields sync from billing and CRM events, so segments stay true without manual passes

Use Case Scenarios

The lead source that finally connects

New responses land in [Typeform](/integrations/typeform) from the lead magnet. For each one, the agent calls Create Subscription with the reader's email, the campaign's UTM parameters, and the custom fields the form captured, then Enroll In Automation to start the welcome series. [Slack](/integrations/slack) tells the growth team what each source produced. When the partner team delivers a spreadsheet instead, the same flow reads [Google Sheets](/integrations/google-sheets) and the list grows the same governed way.

One audience, consistent across the stack

Nightly, the agent pages through List Subscriptions with the cursor, expanding stats and custom fields, and syncs the audience into [Klaviyo](/integrations/klaviyo) profiles. Premium readers, identified by tier, flow into the segments that gate paid-content campaigns. When a subscriber churns from the paid tier in the billing system, Update Subscription downgrades the tier and updates the custom fields the same day, so no campaign ever addresses a reader as something they no longer are.

The newsletter's numbers, where the team actually looks

Monday morning, the agent pulls List Posts for last week's issues with stats expanded, List Segments for audience composition, and assembles the report: what was sent, how it performed, how each segment moved. The digest posts to the growth channel and appends to the reporting sheet. The team stops screenshotting dashboards, and the trend lives in one place with history.

Human-in-Loop Highlight

Delete Subscription permanently removes a subscriber and their data from the publication, and it cannot be undone. It is also, sometimes, exactly what you must do: a data subject requests erasure, and the request is legitimate. The failure mode is an agent treating deletion as list hygiene, purging "inactive" readers along with their stats, referral history, and the record that they ever consented. So FlowRunner flows never call Delete Subscription on pattern-matched criteria. The agent assembles the case: "Erasure request for reader j.doe, subscribed 2024, premium tier until March, referral source of 6 active readers. Delete permanently?" The publication owner confirms the identity and the request, and only then does the deletion run. The [human-in-the-loop](/concepts/human-in-the-loop) gate is the difference between compliance and an unrecoverable mistake.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

12 actions

Subscribers

List Subscriptions Lists a publication's subscribers with exact-email lookup, status and tier filters, cursor pagination, and expandable stats, custom fields, referrals, and newsletter lists. The lookup and sync backbone.
Get Subscription Retrieves one subscriber by subscription ID with the same expandable detail. The context step before any profile decision.
Create Subscription Creates a subscriber, optionally reactivating an unsubscribed reader, sending the welcome email, recording UTM attribution and referring site, and setting existing custom fields. The front door for every growth source.
Update Subscription Updates a subscriber's tier and custom field values, changing only what is provided. The maintenance write that keeps segments truthful.
Delete Subscription Permanently deletes a subscriber and their data. The operation this page's human gate exists for.

Publications and Posts

List Publications Lists the publications the API key can reach, with expandable statistics. The discovery step that scopes everything else.
Get Publication Retrieves one publication's name, organization, and creation date, with optional statistics.
List Posts Lists newsletter issues and web articles with status filters and expandable content and stats. The source for performance reporting.
Get Post Retrieves one post with optional full rendered content and stats. Used when a workflow repurposes or archives an issue.

Segments and Automations

List Segments Lists the saved audience filters defined for a publication, filterable by status and type. The map of how the audience is already divided.
List Automations Lists the publication's subscriber workflows. The reference for finding journeys with active Add by API triggers.
Enroll In Automation Enrolls an existing subscriber into an automation by email or subscription ID, provided the automation has an active Add by API trigger. The step that turns a new signup into an onboarded reader.

Frequently Asked Questions

What can FlowRunner do with beehiiv?

FlowRunner agents can run List Subscriptions, Get Subscription, and Create Subscription in beehiiv, plus 9 more actions.

Does connecting beehiiv to FlowRunner require OAuth?

No. beehiiv connects to FlowRunner with an API key, no OAuth flow required.

Can beehiiv trigger a FlowRunner workflow automatically?

beehiiv doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with beehiiv

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us