Get ManyChat Subscriber: ManyChat action

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
Subscriber ID subscriber_id	string	Required	ManyChat subscriber ID

Sample request

{
  "subscriber_id": "e.g. 123456789012345"
}

Returns

{
  "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.

FAQ

Questions about Get ManyChat Subscriber.

What does the Get ManyChat Subscriber action do in ManyChat?

Returns a subscriber by ID with profile, tags, custom fields. The standard lookup for context-enrichment workflows.

What inputs does Get ManyChat Subscriber require?

Required: Subscriber ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 ManyChat returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get ManyChat Subscriber support batch operations?

Yes. Run Get ManyChat Subscriber inside a Loop node to process arrays. Tiny Command handles ManyChat's rate limits automatically so you don't have to throttle manually.

More actions