Short answer: You can send manychat flow in ManyChat by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ManyChat Send ManyChat Flow action to a workflow, map its 2 inputs 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 |
Flow Namespace flow_ns | string | Required | Flow namespace from the Flow Builder URL |
{"subscriber_id": "e.g. 123456789012345","flow_ns": "content20240101120000_123456"}
{"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.