Actions34
- Page Actions
- Sending Actions
- Subscriber Actions
- Template Actions
Subscriber → findByCustomField
AI-generatedSummary
Look up a ManyChat subscriber on this page whose custom field matches a given value, by calling GET /fb/subscriber/findByCustomField with the field's ID and the target value.
Inputs
- Subscriber ID / selection context — Not used by this operation — findByCustomField searches across all of the page's subscribers rather than targeting one by ID.
- Custom Field (custom_field_mode) (required) — Chooses how the custom field to search on is identified: 'list' (default) to pick one via the connected ManyChat account's custom fields (loaded through the getCustomFieldsById method), or 'id' to type its numeric Field ID manually.
- Custom Field (custom_field_id_list) (required) — Shown when custom_field_mode = 'list'. A dropdown of the page's custom fields (label shows name and type) fetched live via GET /fb/page/getCustomFields; its value is the field's numeric ID.
- Field ID (field_id) (required) — Shown when custom_field_mode = 'id'. Numeric ID of the custom field to search on, entered manually instead of selecting from the list.
- Field Value (find_field_value) (required) — The value to match against the chosen custom field. Sent as the field_value query parameter.
Output shape
One n8n item per input item, each containing the JSON body returned by ManyChat's GET /fb/subscriber/findByCustomField endpoint (typically a status flag plus the matching subscriber data, or an empty/not-found result if no subscriber has that field value).
Raw API response is passed straight through via returnJsonArray — no extra parsing or pagination is applied by the node. If the request fails and 'Continue On Fail' is enabled, the item's json will instead be {"error": "
"} rather than throwing; otherwise a NodeApiError/NodeOperationError is thrown and execution stops.
Examples
Example 1: You store a CRM/order ID in a ManyChat custom field and need to find the subscriber tied to a given order when an external system sends you that order ID.
custom_field_mode = 'list', custom_field_id_list = the 'Order ID' field selected from the dropdown, find_field_value = '{{$json.orderId}}'
Example 2: You already know the numeric custom field ID (e.g. hardcoded from documentation or a prior API call) and want to skip the extra lookup call the dropdown would trigger.
custom_field_mode = 'id', field_id = 10452876, find_field_value = 'VIP'
