Integration
Connect TestLocally to Kloudfox
When something happens in TestLocally, your agent does the next thing in Kloudfox. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want TestLocally and Kloudfox 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 TestLocally and Kloudfox
Triggers and actions 1 trigger ยท 13 actions
Trigger
New TestTriggers when a new test has been requested.
- Find Tests
Finds recent Test Results
- Get Random Locations
Returns a set of 1-9 random Location names
- Get Test Results
Gets the Test Result details
- Request New Test
Request a new screenshot from a set of locations
Action
Add incidentLog a new incident against a monitor/resource. POST /incident/log.
- Add monitor
Create a new uptime/website monitor. POST /monitor/create.
- Delete monitor
Delete a monitor by id. DELETE /monitor/delete.
- Get incident
Retrieve a single incident's details by id. GET /incident/detail.
- Get monitor
Retrieve a single monitor's details by id. GET /monitor/detail.
- List incidents
List incidents on the account. GET /incident/list.
- List monitors
List all monitors on the account. GET /monitor/list.
- List status pages
List status pages on the account. GET /statuspage/list.
- Update monitor
Update an existing monitor's configuration (interval, URL, alert settings). POST /monitor/configure.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.