Short answer: You can get manychat subscriber in ManyChat by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ManyChat Get ManyChat Subscriber 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.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Subscriber ID subscriber_id | string | Required | ManyChat subscriber ID |
{"subscriber_id": "e.g. 123456789012345"}
{"data": {"id": "123456789012345","name": "John Doe","tags": [],"gender": "male","last_name": "Doe","first_name": "John","subscribed": "2025-01-15T12:00:00+0000","profile_pic": "https://example.com/pic.jpg","last_interaction": "2025-04-11T10:00:00+0000"},"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.