Linking beehiiv as a source

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more
PostHog Wizard hedgehog

Alpha release

This source is currently in alpha. The interface and available tables may change.

The beehiiv connector syncs authors, automations, complimentary access, and more into the PostHog data warehouse, so you can analyze them alongside your product data.

Prerequisites

Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.

Adding a data source

  1. In PostHog, go to the Sources tab of the data pipeline section.
  2. Click + New source and click Link next to this source.
  3. Enter your credentials (see Configuration below) and click Next.
  4. Select the tables you want to sync, choose a sync method and frequency, then click Import.

Once the syncs are complete, you can start querying this data in PostHog.

Create an API key in beehiiv under Settings > Integrations > API, then paste it below along with your publication ID. The key needs read access to the resources you want to sync, for example subscriptions:read, posts:read and publications:read. API access requires a paid beehiiv plan.

You'll be asked for:

  • API key
  • Publication ID: for example pub_00000000-0000-0000-0000-000000000000.

Sync modes

Each table can be synced in one of several modes, depending on what the source supports:

  • Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
  • Incremental – only new or updated rows are synced on each run, using a cursor field (such as an updated_at timestamp). Cheaper than a full refresh, but deletes aren't captured.
  • Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
  • Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.

See sync methods for a full explanation of how each mode works and how to choose between them.

All beehiiv tables are full refresh. Each sync replaces the contents of the table.

Configuration

OptionTypeRequired
API keypasswordYes
Publication IDtextYes

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
Authors

Guest authors and team members who can be credited on a publication's posts.

Full refresh——
Automations

Automated journeys that run against subscribers of the publication.

Full refresh——
ComplimentaryAccess

Gifted premium access grants, each tied to a premium tier.

Full refresh——
ConditionSets

Reusable sets of conditions used to target subscribers across beehiiv features.

Full refresh——
CustomFields

Custom field definitions available on the publication's subscriptions.

Full refresh——
NewsletterLists

Newsletter lists that subscribers can belong to within the publication.

Full refresh——
Podcasts

Podcasts belonging to the publication, with their distribution and publishing metadata.

Full refresh——
Polls

Polls that can be embedded in posts and answered by subscribers.

Full refresh——
PostTemplates

Reusable post templates saved on the publication.

Full refresh——
Posts

Newsletter posts, including drafts, scheduled and archived posts, with their email and web engagement stats.

Full refresh——
Publications

Publications in the beehiiv workspace the API key belongs to.

Full refresh——
ReferralProgramMilestones

Milestones in the publication's referral program and the reward each one unlocks.

Full refresh——
Segments

Saved subscriber segments and the result of their most recent calculation.

Full refresh——
Subscriptions

Subscribers of the publication, with the UTM parameters and referral data captured when they signed up.

Full refresh——
Tiers

Premium subscription tiers offered by the publication.

Full refresh——

Troubleshooting

  • If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
  • If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.

If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.

Still have questions?

Was this page useful?