Short answer: Drop the "ManyChat → List ManyChat Subscribers by Tag" 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 |
|---|---|---|---|
Tag ID tag_id | string | Required | Tag ID to filter by |
Limit limit | string | Optional | Max number of subscribers to return (default 100) |
{"tag_id": "e.g. 9876543","limit": "100"}
{"data": [{"id": "123456789012345","last_name": "Doe","first_name": "John"}],"status": "success"}
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.