Integration
Connect CloudConvert to Rendi
When something happens in CloudConvert, your agent does the next thing in Rendi. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want CloudConvert and Rendi 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 CloudConvert and Rendi
Triggers and actions 2 triggers · 9 actions
Trigger
Job FailedTriggers when a job failed.
- Job Finished
Triggers when a job finished.
- Capture a Website
Creates job to capture a website as PDF or create a website screenshot as JPG or PNG.
- Convert a File
Creates job to convert a file.
- Get file metadata
Extract metadata (e.g. page count, dimensions, duration) from a file (metadata operation task).
- Get job
Look up the status and results of a conversion job by ID (GET /v2/jobs/{id}).
Action
Delete FileDeletes one stored file in Rendi by file_id. DELETE /v1/files/{file_id}.
- Get File
Returns the details of one stored file — its status, download link, size, format and media properties.
- List Commands
Lists FFmpeg commands previously sent to Rendi. GET /v1/commands.
- Poll FFmpeg Command
Get the status of a previously submitted FFmpeg command
- Run FFmpeg Command
Submit an FFmpeg command for processing with input and output file specifications
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