ActionMailerLiteUpdated September 2026
What MailerLite groups exist?
Short answer: You can list mailerlite groups in MailerLite by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the MailerLite List MailerLite Groups action to a workflow, map its 1 input 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 |
|---|---|---|---|
Limit limit | number | Optional | Limit |
Sample request
{"limit": "{{trigger.limit}}"}
Returns
{"data": [{"id": "grp123","name": "Newsletter","open_rate": {"float": 25.5},"sent_count": 12,"active_count": 5000}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List MailerLite Groups.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List MailerLite Groups.
What does the List MailerLite Groups action do in MailerLite?
Returns every group on the account with subscriber count. Useful for resolving group IDs at workflow setup.
What inputs does List MailerLite Groups require?
List MailerLite Groups has no required inputs. Sensible defaults are applied if you leave fields blank.
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 MailerLite returns an error?
The run history shows the failed step with its input and the error message MailerLite 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 List MailerLite Groups support batch operations?
Run List MailerLite Groups 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 MailerLite's rate limits.
More actions