Short answer: Drop the "ManyChat → Set ManyChat Custom Field" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
Custom Field ID field_id | string | Required | Custom field ID (numeric) |
Value field_value | string | Required | Value to set |
{"subscriber_id": "e.g. 123456789012345","field_id": "e.g. 12345","field_value": "any value"}
{"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.
Triggered by anything in the catalog. Free tier available. No credit card.