Short answer: Drop the "Beehiiv → Create Subscriber" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Email email | Required | The email address. Used as the recipient or identifier depending on context. | |
UTM Source utm_source | string | Optional | UTM Source. e.g. "website" |
Reactivate Existing reactivate_existing | boolean | Optional | Reactivate Existing |
{"email": "e.g. user@example.com","utm_source": "website","reactivate_existing": "{{trigger.reactivate_existing}}"}
{"data": {"id": "sub123","email": "john@example.com","status": "active","created_at": "2026-04-11T10:00:00Z"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.