mailchimp

Mailchimp Marketing API integration with managed OAuth. Access audiences, campaigns, templates, automations, reports, and manage subscribers. Use this skill when users want to manage email marketing, subscriber lists, or automate email campaigns. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Mailchimp connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Mailchimp action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Mailchimp examples; they add no Mailchimp capability - Mailchimp is not an event source, a trigger cannot read Mailchimp data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).

Install only if you are comfortable using Maton as the gateway to your Mailchimp account. Review every write, campaign send, function deploy, trigger, or destination before approving it, because these can change subscriber data, send real email, or create ongoing automation. Prefer the CLI/OAuth flow over raw API keys, and delete unused connections, functions, triggers, and destinations when finished.