Short answer: You can create mailerlite subscriber in MailerLite by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the MailerLite Create MailerLite 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.
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. | |
Name name | string | Optional | Name |
Status status | options | Optional | Status. Options: Active, Unsubscribed, Unconfirmed |
{"email": "e.g. user@example.com","name": "{{trigger.name}}","status": "{{trigger.status}}"}
{"data": {"id": "sub123","email": "john@example.com","status": "active","subscribed_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.