Systeme.io MCP integration for AI agents.
Connect AI agents to Systeme.io through 24 structured actions, including get contact, create contact, cancel subscription, and attach contact tag. Review aut…
- ACTION CONTRACTS
- 24
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Systeme.io integration exposes
The Systeme.io Agent App exposes 24 provider-backed actions for marketing and productivity work. Its current contract lets an authorized agent get a systeme.io contact, create a systeme.io contact, and cancel a systeme.io subscription. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Systeme.io account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Systeme.io capabilities.
Showing 12 of 24 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_contactREADGet a Systeme.io contact.
create_contactWRITECreate a Systeme.io contact.
cancel_subscriptionHIGH IMPACTCancel a Systeme.io subscription.
attach_contact_tagREVIEWAttach a tag to a Systeme.io contact.
create_enrollmentWRITECreate a course enrollment in Systeme.io.
create_tagWRITECreate a Systeme.io tag.
create_webhookWRITECreate a Systeme.io webhook.
delete_contactHIGH IMPACTDelete a Systeme.io contact.
delete_enrollmentHIGH IMPACTDelete a course enrollment in Systeme.io.
delete_tagHIGH IMPACTDelete a Systeme.io tag.
delete_webhookHIGH IMPACTDelete a Systeme.io webhook.
detach_contact_tagREVIEWDetach a tag from a Systeme.io contact.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Contact
Get a Systeme.io contact. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_contactControl Create Contact
Create a Systeme.io contact. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_contactVerify with Create Contact
Create a Systeme.io contact. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_contactSAFETY BOUNDARY
Operate Systeme.io with explicit limits
- Authorize Systeme.io with API key and grant only the provider access required by the selected actions.
- 12 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `cancel_subscription`, `delete_contact`, and `delete_enrollment` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Systeme.io rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Systeme.io task completed successfully.
CONNECTION MODEL
API key
Systeme.io API key passed as the X-API-Key header. Create and manage API keys from account settings.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 10
- WRITE SIGNALS
- 7
- HIGH IMPACT
- 5
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Systeme.io.