Integrations · API

Connect Beehiiv to Well

Push person record into Well through Beehiiv, ready to query and act on in your workspace.

What Well pulls from Beehiiv

Beehiiv feeds person record into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Beehiiv’s access.

From Beehiiv		In Well	Relation
Person record		Contact	Resolves to

Sync mode: incremental polling
Refresh: scheduled
Direction: Beehiiv → Well

What Well does with your Beehiiv connection

Connect

Connect Beehiiv over API key: you generate a Beehiiv key and paste it into Well, where it is stored encrypted at rest and never returned in responses.

Sync

Well brings person record in from Beehiiv on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.

Enrich

Well resolves each Beehiiv entity into contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Beehiiv lands in the workspace as contact you can search, chart, and automate.

Questions Beehiiv unlocks

Ask in plain language. Well answers from your connected Beehiiv connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Beehiiv connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Beehiiv connection…

1 agent skill runs on Beehiiv.

Well lists Beehiiv in the connection check every skill runs before it answers. No skill reads it for a figure yet.

Connects and checks Beehiiv

Check your connections

See what is connected, what is syncing, and what is missing.

Browse all skills

Connect Beehiiv in three steps

01
Generate an Beehiiv API key
In Beehiiv, generate an API key with the scopes Well lists in the trust section below. In Well's Connections > Beehiiv, paste the key. Well validates it against Beehiiv's API and confirms with a sample fetch.
- AuthAPI key
- Validationsample fetch on save
02
Map your entities
Well brings person record from Beehiiv into your workspace using the canonical mappings defined in Well's data-views layer.
- Mappingpreconfigured by Well
03
Use the data
Use what you bring in from Beehiiv in conversation, records tables, or agent runs. Rotating the key in Beehiiv requires updating the key in Well; nothing else.
- First syncstarts as soon as connect completes

Keys are never returned in API responses. Rotate freely; Well will prompt for the new key.

How Beehiiv stays secure with Well

Well calls Beehiiv with the API key you provision, scoped to person record. The key is never logged and never returned in API responses. Beehiiv validates the key on every request; rotating the key in Beehiiv immediately invalidates Well's access. No write access unless the key explicitly grants it.

API keyEncrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requests

Read Beehiiv records
Endpoints the Beehiiv API token grants, scoped by your consent.
granted
Resolve person record across your stack
Match identifiers in Beehiiv against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Beehiiv records
Not granted; Beehiiv is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Read API keys from Beehiiv's settings
Well only sees the keys you paste in. The keys never leave Well's secret store back to Beehiiv's admin surface.
refused

Disconnect any time from Well settings or Beehiiv’s admin panel.

Frequently asked questions about Beehiiv and Well

How do I connect Beehiiv to Well, and how long does it take?

In Beehiiv, generate an API key with read access (scoped to what's listed in the security section below). In Well, open Connections > Beehiiv, paste the key, and save. Well validates the key against Beehiiv's API and pulls a first sample as confirmation.

What does Well pull into the workspace from Beehiiv?

Well brings in person record from Beehiiv and reshapes each entity into your workspace: person record becomes contact. Every record arrives with the source identifier preserved, so Beehiiv stays the source of truth while Well lets you query the data alongside the rest of your stack.

What does Beehiiv unlock once it is connected to Well?

Once Beehiiv is connected, every record it exposes is queryable from conversation, filterable in records tables, and available to your agents through your workspace. The data stays linked to its Beehiiv source, so you can always trace a workspace record back to the original.

How does Well match a person record from Beehiiv to a contact in my workspace?

Each Beehiiv person record is scored against the candidate contacts in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely contact prefilled and the Beehiiv source attached.

How often does Beehiiv sync with Well, and what triggers a refresh?

Well polls Beehiiv regularly for person record. The first connect pulls the historical window your account allows; subsequent reads only fetch what changed since the last sync, so the load on Beehiiv's side stays modest.

Can I disconnect Beehiiv and what happens to the data Well already pulled?

Open Connections > Beehiiv in Well, click Disconnect, then rotate the API key on Beehiiv's side. Well stops calling Beehiiv as soon as you disconnect; rotating the key on the provider's side guarantees Well cannot resume access. The person record already synced stay in your workspace until you ask Support to purge them.

How does Well protect what it pulls in from Beehiiv?

The Beehiiv records Well holds are encrypted at rest and handled in line with GDPR. See /privacy for the current data-handling policy.