kit

Kit (formerly ConvertKit) API integration with managed OAuth. Manage email subscribers, forms, tags, sequences, broadcasts, custom fields, purchase records, and webhooks. Webhook creation sends Kit account events to a URL you supply, and the purchase endpoints expose customer and order data. Use this skill when users want to manage their email marketing lists, create or update subscribers, manage tags, or work with email sequences and broadcasts. 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 Kit connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Kit 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 Kit examples; they add no Kit capability - Kit is not an event source, a trigger cannot read Kit 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 intend to let Maton access your Kit account. Review every requested write, broadcast, sequence enrollment, webhook, trigger, or destination carefully, because those actions can send email, change audience data, or forward future subscriber/event data until removed.