ActionBeehiivUpdated September 2026
How do I add a subscriber to Beehiiv?
Short answer: You can create subscriber in Beehiiv by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Beehiiv Create Subscriber action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
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 |
Sample request
{"email": "e.g. user@example.com","utm_source": "website","reactivate_existing": "{{trigger.reactivate_existing}}"}
Returns
{"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.
Triggered by
Apps that pair well as the trigger for Create Subscriber.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Create Subscriber.
What does the Create Subscriber action do in Beehiiv?
Adds a new subscriber to a publication with optional custom fields, referral code, and referring site. The standard hook for "form submission → push to newsletter" workflows. Beehiiv's referral attribution makes this useful for partner-promo flows too.
What inputs does Create Subscriber require?
Required: Email. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Beehiiv returns an error?
The run history shows the failed step with its input and the error message Beehiiv returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Create Subscriber support batch operations?
Run Create Subscriber inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Beehiiv's rate limits.
More actions