Integration
Connect Conversion Tools to Kloudfox
When something happens in Conversion Tools, 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 Conversion Tools 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 Conversion Tools and Kloudfox
Triggers and actions 4 triggers ยท 11 actions
Trigger
Conversion FailedTriggered when a file conversion fails, giving the reason it failed.
Trigger
Conversion Result AvailableTriggered when a finished conversion has its result file ready to download.
Trigger
Conversion StartedTriggered when a new file conversion is submitted, while it is still queued or running.
Trigger
Conversion Successfully FinishedTriggered when a file conversion finishes successfully.
Action
Convert FileUploads a file to Conversion Tools and starts converting it, returning the conversion ID. Use one of the result triggers or Convert File and Get the Result to pick up the converted file.
Action
Convert File and Get the ResultUploads a file to Conversion Tools, converts it, waits for the conversion to finish and returns a link to download the result.
Action
Add incidentLog a new incident against a monitor/resource. POST /incident/log.
Action
Add monitorCreate a new uptime/website monitor. POST /monitor/create.
Action
Delete monitorDelete a monitor by id. DELETE /monitor/delete.
Action
Get incidentRetrieve a single incident's details by id. GET /incident/detail.
Action
Get monitorRetrieve a single monitor's details by id. GET /monitor/detail.
Action
List incidentsList incidents on the account. GET /incident/list.
Action
List monitorsList all monitors on the account. GET /monitor/list.
Action
List status pagesList status pages on the account. GET /statuspage/list.
Action
Update monitorUpdate 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.