ManyChat

**Judgment:** This skill is a strong, well-documented integration for ManyChat via the Maton gateway, suitable for production use when you need structured, programmatic control over ManyChat subscribers, tags, custom fields, flows, and messaging. **What it’s good at:** - Managing the full subscriber lifecycle: create/update subscribers, add/remove tags, and set single or multiple custom fields. - Controlling ManyChat automation: listing and triggering flows, managing bot/global fields, and working with growth tools and OTN topics. - Sending structured messages (text, images, quick replies, buttons) and flows via Messenger with explicit handling of message tags and 24-hour window rules. - Being language-agnostic: you call standard HTTPS endpoints; examples are provided for JavaScript and Python. **Key risks & limitations:** - **External dependency:** Relies on Maton’s gateway and control plane; outages or changes there impact reliability. You must manage a MATON_API_KEY and ManyChat connection in Maton. - **PII handling:** Subscriber data (names, phones, emails) and consent information flows through this integration. You need to handle storage, access control, and logging in a compliant way (e.g., GDPR/CCPA where relevant). - **Irreversible/bulk operations:** Removing tags from the page or subscribers, or updating many custom fields, can have large-scale effects that are not easily reversible. - **Rate limits:** Many endpoints have per-second limits; heavy or bulk workloads should batch and backoff correctly to avoid 429s. **Recommended scenarios:** - Teams already using ManyChat for Facebook Messenger who want to centralize automation or CRM syncing through a server-side or workflow-based integration. - Projects that need to trigger ManyChat flows or send messages based on external events (purchases, support tickets, webhooks, etc.). - Building internal tools for marketers or support staff to view and manage ManyChat subscriber data, segmentation tags, and automation settings without exposing raw API keys. **When to be cautious or consider alternatives:** - If you cannot or do not want to depend on Maton’s infrastructure (e.g., strict vendor or data residency requirements), direct integration with ManyChat’s API may be preferable. - If your use case involves extremely high-throughput messaging or near-real-time workloads, you may need to carefully design around the documented rate limits and monitor performance/latency.