Integration
Connect systeme.io to Xitoring
When something happens in systeme.io, your agent does the next thing in Xitoring. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want systeme.io and Xitoring to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with systeme.io and Xitoring
Triggers and actions 1 trigger ยท 26 actions
Trigger
New Tag Added to ContactTriggers when a tag is added to contact.
Action
Add digital productCreate a new payment Digital Product resource. POST /api/payment/digital-products
Action
Add tag to contactAssign an existing Tag to a Contact by id (distinct from create-or-update-with-tags). POST /api/contacts/{id}/tags
Action
Create or Update a Contact, Including Adding TagsCreates a contact in systeme.io, or updates the existing contact with that email address, and applies any tags you list.
Action
Delete contactRemove a Contact resource by id. DELETE /api/contacts/{id}
Action
Find contacts by emailSearch Contact resources filtered by email address. GET /api/contacts?email=
Action
Get contactRetrieve a single Contact resource by id. GET /api/contacts/{id}
Action
List contactsRetrieve the collection of Contact resources, paginated. GET /api/contacts
Action
List digital productsRetrieve the collection of payment Digital Product resources. GET /api/payment/digital-products
Action
List tagsRetrieve the collection of Tag resources. GET /api/tags
Action
Remove TagRemoves tag from a contact
Action
Add checkCreate a new uptime/website/server check. POST /api/v2/check
Action
Add groupStore a new check/server group. POST /api/v2/groups
Action
Add heartbeatCreate a new heartbeat check. POST /api/v2/heartbeat/add
Action
Add maintenance scheduleCreate a new maintenance window. POST /api/v2/maintenance-schedules/add
Action
Add ticketCreate a new support ticket. POST /api/v2/tickets
Action
Delete checkDelete a check. DELETE /api/v2/checks/{id}
Action
Delete serverRemove a server from monitoring. DELETE /api/v2/servers/{id}
Action
Get checkRetrieve a single check by id. GET /api/v2/check/{id}
Action
Get incidentGet a single incident's data. GET /api/v2/incidents/{id}
Action
Get serverRetrieve a single server by id. GET /api/v2/servers/{id}
Action
List checksList all checks. GET /api/v2/check/
Action
List groupsList all groups. GET /api/v2/groups
Action
List maintenance schedulesList maintenance schedules. GET /api/v2/maintenance-schedules
Action
List serversList all monitored servers. GET /api/v2/servers
Action
Resolve incidentResolve an open incident. POST /api/v2/incidents/{id}/resolve
Action
Update checkUpdate an existing check. PUT /api/v2/check/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews