Send ManyChat Content: 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
Message Text text	string	Required	Text content to send to the subscriber
Message Tag message_tag	options	Optional	Required by Facebook outside the 24-hour window

Sample request

{
  "subscriber_id": "e.g. 123456789012345",
  "text": "Hi there!",
  "message_tag": "{{trigger.message_tag}}"
}

Returns

{
  "status": "success"
}

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

FAQ

Questions about Send ManyChat Content.

What does the Send ManyChat Content action do in ManyChat?

Sends pre-configured content (cards, buttons, media) from the ManyChat library to a subscriber. For "trigger this specific content card based on external signal" workflows.

What inputs does Send ManyChat Content require?

Required: Subscriber ID, Message Text. 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 Send ManyChat Content support batch operations?

Yes. Run Send ManyChat Content 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