Marketing & email · wired today

beehiiv, wired into your agent workforce

Campaign and audience data drives half the questions agents get asked. The beehiiv connector is one of 222 executable connectors and gives agents 3 read-only tools, with the credential held in the vault and every call receipted.

Connecting beehiiv takes one credential

You provide API key from your beehiiv account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Where to get it: beehiiv's own API documentation ↗ covers creating and scoping the credential.

What agents can run against beehiiv

list_publications

List the beehiiv publications the API key can access (id, name, organization, created date)

list_posts

List posts belonging to one beehiiv publication, optionally filtered by status

list_subscriptions

List subscriptions for one beehiiv publication, optionally filtered by status, tier or exact email

Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.

How proven is this?

This connector was blind shape-proven against the real beehiiv API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.

Credentialed The vault stores, tests and just-in-time resolves its credential; agents never see the secret.
Read-only It ships read tools only, so there is nothing to approval-gate.
Agent-owned No dedicated agent owns it yet; the orchestrator can drive it on request.
Schedulable Not yet exposed in the workflow builder; that integration is on the connector roadmap.
Evidenced Per-call evidence envelopes are on the roadmap; vault credential use is already receipted.

beehiiv integration FAQ

What can Quox agents do with beehiiv?

Agents can run 3 read-only tools against beehiiv: list publications, list posts, list subscriptions. Every call is receipted in the evidence trail.

What does the beehiiv integration need?

You provide API key from your beehiiv account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.

Do agents see my beehiiv credentials?

No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.

How proven is the beehiiv connector?