Integration
Connect StatusCake to Wachete
When something happens in StatusCake, your agent does the next thing in Wachete. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want StatusCake and Wachete 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 StatusCake and Wachete
Triggers and actions 4 triggers · 24 actions
Trigger
New Latest Page Speed TestTriggers when a new test is created, and provides basic pagespeed test data information.
Trigger
New Latest SSL TestTriggers when a new test is created, and provides basic ssl test data information.
Action
Add contact groupCreate a new contact group for alert notifications. POST /contact-groups
Action
Create Page Speed TestCreates a new pagespeed test for your StatusCake account.
Action
Create SSL TestCreates a new SSL test for your StatusCake account.
Action
Create Uptime TestCreates a new uptime test for your StatusCake account.
Action
Delete contact groupDelete a contact group by id. DELETE /contact-groups/{id}
Action
Delete page speed testDelete a pagespeed check by id. DELETE /pagespeed/{id}
Action
Delete SSL testDelete an SSL check by id. DELETE /ssl/{id}
Action
Delete uptime testDelete an uptime check by id. DELETE /uptime/{id}
Action
Get contact groupRetrieve a single contact group by id. GET /contact-groups/{id}
Action
Get page speed testRetrieve a single pagespeed check by id. GET /pagespeed/{id}
Action
Get SSL testRetrieve a single SSL check by id. GET /ssl/{id}
Action
Get uptime testRetrieve a single uptime check by id. GET /uptime/{id}
Action
List contact groupsList all contact groups for the account. GET /contact-groups
Action
List SSL testsList all SSL checks for the account. GET /ssl
Action
Update contact groupUpdate an existing contact group by id. PUT /contact-groups/{id}
Action
Update page speed testUpdate an existing pagespeed check by id. PUT /pagespeed/{id}
Action
Update uptime testUpdate an existing uptime check by id. PUT /uptime/{id}
Trigger
Any new notificationFires when there is a new change notification from any monitor in your Wachete account.
Trigger
New notification for monitorFires when there is a new change notification from the specified Wachete monitor (taskId).
Action
Create monitorCreate a new Wachete monitor (wachet) that watches a web page or part of a page for changes.
Action
Delete monitorDelete a Wachete monitor by its ID.
Action
Get monitorGet information about a specific Wachete monitor by its ID.
Action
Get monitor dataGet the captured data/history for a Wachete monitor, optionally as a diff and within a date range.
Action
List foldersList folder contents, optionally under a parent folder.
Action
List notificationsList change notifications, optionally filtered by monitor (taskId) and date range.
Action
Update monitorChange the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.