Find ManyChat Subscriber by Name: 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
Name name	string	Required	Full or partial name to search

Sample request

{
  "name": "John Doe"
}

Returns

{
  "data": [
    {
      "id": "123456789012345",
      "last_name": "Doe",
      "first_name": "John"
    }
  ],
  "status": "success"
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Find ManyChat Subscriber by Name.

What does the Find ManyChat Subscriber by Name action do in ManyChat?

Lookup by partial name match. Useful for sales workflows that need to find a known subscriber to push a message.

What inputs does Find ManyChat Subscriber by Name require?

Required: Name. 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 Find ManyChat Subscriber by Name support batch operations?

Yes. Run Find ManyChat Subscriber by Name 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