Systeme.io

**Judgment**: This skill is a solid, well-documented Systeme.io integration via the Maton gateway, suitable for production-style automation of contacts, tagging, courses, communities, and subscriptions, assuming the user can supply a valid MATON_API_KEY and has configured a Systeme.io connection. **What it’s good for** - Running end-to-end CRM-style flows: create/update contacts, manage tags and custom fields, and keep Systeme.io contact data in sync with other tools. - Educational and community platforms: enroll contacts into courses, manage access modes, and control community memberships programmatically. - Subscription lifecycle management: list active subscriptions and cancel them when triggered by business logic (refunds, failed payments, churn workflows). - Bulk or incremental operations where the agent pages through contacts/tags/enrollments using the documented cursor-based pagination. **Key strengths** - Covers the main objects most users care about in Systeme.io (contacts, tags, fields, courses/enrollments, communities/memberships, subscriptions). - Clear, concrete HTTP examples (Python and JavaScript) and detailed request/response patterns help the agent infer correct usage. - Managed OAuth and header translation remove much of the complexity of talking to Systeme.io directly. **Risks and limitations** - Requires a Maton account and a valid MATON_API_KEY; without that, all calls will fail (typically 401 or 400 for missing connection). - Handles personal data (emails, phone numbers, subscription details), so prompts and tool calls must be written to avoid unnecessary data exposure or logging. - Rate limits and passthrough 4xx/5xx errors are possible; the agent should be prepared to inspect response codes and back off or explain failures. - The documented scope is focused on core CRM/course/community/subscription operations; more advanced Systeme.io features (e.g., funnels, email campaigns, automations) are not clearly exposed here and may require the separate api-gateway skill. **Recommended scenarios** Use this skill when the user explicitly mentions Systeme.io or clearly wants to manage contacts, tags, courses/enrollments, communities, or subscriptions in Systeme.io and they (or the environment) can supply the Maton API key. For other SaaS APIs or non-Systeme.io operations, prefer the separate api-gateway skill as instructed in the metadata.