Integration
Connect Conversion Tools to PurgoMalum
When something happens in Conversion Tools, your agent does the next thing in PurgoMalum. 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 PurgoMalum 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 PurgoMalum
Triggers and actions 4 triggers ยท 4 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
Check text for profanityCheck whether the given text contains any words matching PurgoMalum's profanity list, returning true or false (GET /service/containsprofanity, optional add param).
Action
Filter profanity from textRemove or replace profane words in the given text using PurgoMalum's profanity list, returning the cleaned text (GET /service/json, optional add/fill_text/fill_char params).
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