Integration
Connect CloudConvert to TemplateDocs
When something happens in CloudConvert, your agent does the next thing in TemplateDocs. 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 TemplateDocs 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 TemplateDocs
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
Add templateUploads a Word document to TemplateDocs as a new template, and returns the template's id along with the placeholders found inside it.
- Delete template
Removes a template from your TemplateDocs account.
- Get template
Returns the details of one template, including its name, size, checksum and the placeholder tags it contains.
- List templates
Returns the templates available in your TemplateDocs account, each with its name, size and placeholder tags.
- Update template
Renames a template or changes its settings. Returns the id of the template that was updated.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.