Add Subscriber to Group
mailerlite.assign_subscriber_to_group
ActionEmailconnection required
Calls the MailerLite API with the connection's credentials.
Add an existing subscriber to an existing group.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Bearer token
- Providers
- MailerLite
- Secret shape
- the API token, or {"api_key": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
subscriber_id The subscriber's MailerLite id. | string | Yes | — | — | 31982639460318841 |
group_id The group's MailerLite id. | string | Yes | — | — | 123456789 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"group_id": "123456789",
"subscriber_id": "31982639460318841"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
assigned True when MailerLite accepted the assignment. | boolean | — |
subscriber_id The subscriber that was added. | string | — |
group_id The group they were added to. | string | — |
group The group record MailerLite returned. | object | — |
{
"assigned": false,
"group": {},
"group_id": "",
"subscriber_id": ""
}See Add Subscriber to Group run in a workflow.
In a technical demo we add the MailerLite connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.