Beehiiv currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to connect campaign activity to the records and follow-up it should influence.
New Post Sent
Triggers when a new post is sent.
User Unsubscribes
Triggers when a user unsubscribes.
New Subscription Confirmation
Triggers when a new subscriber confirms their subscription.
Create Subscription
Creates a new subscription.
Update Subscription
Update an existing subscription.
Add Subscription to Automation
Adds an existing subscription to a specific automation flow.
List Automations
Retrieves a list of automations for a publication.
List Posts
Retrieves all posts belonging to a specific publication.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Beehiiv event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Post Sent
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Beehiiv action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Subscription
Combine Beehiiv with another integration and Coherence records to connect campaign activity to the records and follow-up it should influence.
Starts with
New Post Sent
Finishes with
Create Subscription, then preserve the outcome in Coherence
The exact authentication fields depend on Beehiiv. The workflow structure stays straightforward:
Authorize the Beehiiv account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Beehiiv or provide a complementary trigger or action.
Beehiiv currently provides 3 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to connect campaign activity to the records and follow-up it should influence.
Beehiiv currently lists 3 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Beehiiv triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
