Overview
This node acts as a trigger for workflows based on events from Beehiiv, a newsletter and subscription platform. It listens for specific webhook events sent by Beehiiv and starts the workflow when those events occur. This is useful for automating processes such as sending notifications, updating databases, or triggering other actions in response to changes in your Beehiiv account.
Common scenarios include:
- Triggering a workflow when a new post is sent to subscribers.
- Reacting to subscription lifecycle events like creation, confirmation, upgrade, downgrade, or deletion.
- Handling survey responses submitted by subscribers.
For example, you could use this node to automatically add new confirmed subscribers to a CRM system or send a Slack message whenever a new post is published.
Properties
| Name | Meaning |
|---|---|
| Events | Select one or more Beehiiv event types to listen for. Options include: |
- post.sent: Receive notifications when a new Beehiiv post is sent |
|
- subscription.confirmed: Receive notifications when a Beehiiv subscription is confirmed |
|
- subscription.created: Receive notifications when a Beehiiv subscription is created |
|
- subscription.deleted: Receive notifications when a Beehiiv subscription is deleted |
|
- subscription.downgraded: Receive notifications when a Beehiiv subscription is downgraded |
|
- subscription.upgraded: Receive notifications when a Beehiiv subscription is upgraded |
|
- survey.response_submitted: Receive notifications when a Beehiiv survey response is submitted |
Output
The node outputs the webhook payload received from Beehiiv as JSON data. The output structure directly reflects the event data sent by Beehiiv for the selected event(s). This allows downstream nodes to access all relevant information about the event, such as subscriber details, post content, or survey responses.
If binary data were involved, it would be summarized here, but this node only outputs JSON data.
Dependencies
- Requires an API key credential for authenticating with the Beehiiv API.
- Needs to be configured with a publicly accessible webhook URL so Beehiiv can send event notifications.
- The node internally uses the Beehiiv API to manage webhook subscriptions.
Troubleshooting
- Webhook not triggering: Ensure that the webhook URL is correctly set up and publicly accessible. Verify that the selected events are enabled in Beehiiv and that the API key has sufficient permissions.
- Authentication errors: Confirm that the API key credential is valid and has not expired or been revoked.
- No data received: Check that the correct events are selected and that Beehiiv is actually sending event notifications for those events.
- Webhook registration failures: If the node cannot create or verify webhooks via the API, check network connectivity and API rate limits.
Links and References
- Beehiiv API Documentation (for detailed info on events and webhook setup)
- n8n Webhook Node Documentation (general webhook usage in n8n)