ManyChat icon

ManyChat

Consume issues from the ManyChat API

Subscriber → Create A Unified Subscriber

AI-generated

Summary

Create a unified subscriber in ManyChat

Inputs

  • authentication (required) — Credentials for ManyChat API access
  • first_name — First name of the subscriber. Optional; phone or email must be provided per ManyChat requirements.
  • last_name — Last name of the subscriber. Optional.
  • phone — Phone number is required if email and whatsapp phone properties are empty.
  • whatsapp_phone — WhatsApp phone number is required if email and phone properties are empty.
  • email — Email is required if phone number and whatsapp phone properties are empty.
  • gender — Gender of the subscriber. Options: empty, male, female, other.
  • has_opt_in_sms — Has opt-in SMS is required if property phone number is not empty. Default: true.
  • has_opt_in_email — Has opt-in email is required if property email is not empty. Default: true.
  • consent_phrase — Consent phrase is required if property has_opt_in_sms equals true. Shown only when has_opt_in_sms is true.
  • requestOptions — Collection of advanced request settings including batching, proxy, timeout, and SSL validation.

Output shape

Created subscriber object as returned by the ManyChat API; exact payload shape not defined in the node source. Consult ManyChat API documentation for response format.

If both phone and email are empty, the ManyChat API will reject the request. At least one contact method (phone or email) must be provided.

Examples

Example 1: Create a subscriber with name and phone

first_name: 'Alice', last_name: 'Smith', phone: '+15551234567'

Links

Discussion