List Group Subscribers

mailerlite.list_group_subscribers
ActionEmailconnection required

Calls the MailerLite API with the connection's credentials.

List one cursor page of the subscribers that belong to a 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

4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
group_id
The group's MailerLite id.
stringYes——123456789
status
Return only members in this state; omit for every state.
stringNo—one of "active", "unsubscribed", "unconfirmed", "bounced", "junk"—
limit
How many members to return; MailerLite defaults to 25.
numberNo251–1000—
cursor
The next_cursor from a previous run, to read the following page.
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "group_id": "123456789",
  "limit": 25
}

Output

One shape.

result

FieldTypeExample
items
The records on this page, exactly as MailerLite returned them.
array—
count
How many records this page carried.
number—
next_cursor
Cursor to pass back for the next page; empty on the last page, and always empty on the endpoints MailerLite pages by number instead (groups, activity).
string—
prev_cursor
Cursor for the previous page; empty on the first page, and always empty on the endpoints MailerLite pages by number instead (groups, activity).
string—
total
Total matching records when the endpoint reports one, otherwise null.
number—
{
  "count": 0,
  "items": [],
  "next_cursor": "",
  "prev_cursor": "",
  "total": 0
}

See List Group Subscribers 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.