systemeSysteme.io API integration with managed OAuth. Manage contacts, contact tags, contact custom fields, tags, course enrolments, community memberships, and subscriptions. Use this skill when users want to manage Systeme.io contacts, enroll students in courses, manage community memberships, or handle subscriptions. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Requires network access and valid Maton API key. 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 Systeme.io connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Systeme.io 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 Systeme.io examples; they add no Systeme.io capability - Systeme.io is not an event source, a trigger cannot read Systeme.io 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 via ClawdBot CLI:
clawdbot install byungkyu/systemeGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://clawhub.ai/byungkyu/api-gatewayUses known external API (expected, informational)
discord.comAudited Apr 17, 2026 · audit v1.0
Generated Mar 21, 2026
A digital marketing agency uses the skill to manage contact lists and tags for targeted email campaigns. They create custom contact fields to segment audiences based on purchase history, then assign tags to automate follow-up sequences for leads, improving campaign personalization and conversion rates.
An e-learning platform integrates the skill to automatically enroll students in Systeme.io courses upon payment. It creates contacts for new students, assigns them to specific course tags, and updates their progress fields, streamlining the onboarding process and reducing manual administrative work.
A subscription-based community uses the skill to handle member sign-ups and renewals. It manages contacts for members, assigns tags based on membership tiers, and syncs with community access controls, ensuring seamless member onboarding and retention tracking.
A small business owner employs the skill to sync customer data from their website to Systeme.io. They create and update contacts with custom fields for sales leads, tag high-value customers for priority support, and automate contact deletion for inactive users, enhancing customer relationship management.
A SaaS company uses the skill to manage user subscriptions and automate customer lifecycle processes. They integrate it with their platform to handle contact updates, tag users based on usage tiers, and trigger renewal reminders, driving recurring revenue through efficient subscription management.
A marketing agency leverages the skill to offer Systeme.io automation as a service to clients. They set up and manage connections, create custom contact fields, and run tag-based campaigns, generating revenue through monthly retainer fees or project-based billing for enhanced client engagement.
A freelance consultant uses the skill to help small businesses optimize their Systeme.io workflows. They provide setup, integration, and maintenance services, such as creating contact management systems and automating tag assignments, earning income through hourly rates or fixed project contracts.
💬 Integration Tip
Ensure the MATON_API_KEY is securely set as an environment variable and use the Maton-Connection header for multiple Systeme.io accounts to avoid conflicts in API requests.
Scored Sep 28, 2026
Self-hosted auth for TypeScript/Cloudflare Workers with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Requires Drizzle ORM or Kysely for D1 (no direct adapter). Self-hosted alternative to Clerk/Auth.js. Use when: self-hosting auth on D1, building OAuth provider, multi-tenant SaaS, or troubleshooting D1 adapter errors, session caching, rate limits, Expo crashes, additionalFields bugs.
Clerk integration. Manage Users, Organizations. Use when the user wants to interact with Clerk data.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Sentry API integration with managed authentication. Monitor errors, issues, and application performance. Use this skill when users want to list issues, retrieve events, manage projects, teams, or releases in Sentry. 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 Sentry connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Sentry 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 Sentry examples; they add no Sentry capability - Sentry is not an event source, a trigger cannot read Sentry 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).
Download YouTube videos by URL in various resolutions using a pay-per-use API with credit-based authentication and no charge on failed downloads.
OneNote API integration with managed OAuth via Microsoft Graph. Access notebooks, sections, section groups, and pages. Use this skill when users want to create or manage OneNote notebooks, organize notes, or work with page content. 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 an OneNote connection into automation, in the order they are used: the connection (the first step), a hosted function that runs an OneNote 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 OneNote examples; they add no OneNote capability - OneNote is not an event source, a trigger cannot read OneNote 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).