Integration
Connect Givebutter to Xitoring
When something happens in Givebutter, 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 Givebutter 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 Givebutter and Xitoring
Triggers and actions 4 triggers ยท 17 actions
Trigger
New CampaignTriggers when a new campaign is created.
Trigger
New TicketTriggers when a new ticket is issued.
Trigger
New TransactionTriggers when a new transaction is created.
Trigger
Updated CampaignTriggers when a campaign is updated.
Action
Create ContactCreates a Contact. If there is a contact that already exists with the same First and Last Name, as well as the same Email Or Phone, we will automatically deduplicate and merge the contact, otherwise a new contact will be created. If you'd like to always create a new contact regardless of the deduplication logic, pass the force_create parameter as true.
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.