Short answer: Drop the "Buttondown → 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. | |
Tags tags | string | Optional | Comma-separated |
{"email": "e.g. user@example.com","tags": "lead, premium"}
{"id": "sub123","creation_date": "2026-04-11T10:00:00Z","email_address": "john@example.com","subscriber_type": "regular"}
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.