File conversion and processing platform supporting 200+ formats
CloudConvert currently provides 3 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
New Job Event
Triggers when a new job has been created
Job Finished
Triggers when a CloudConvert job has been completed
Job Failed
Triggers when a CloudConvert job has failed
Convert File
Create a basic file conversion task for a single file with desired output format
Capture Website
Capture webpage as PDF, screenshot PNG, or JPG from a URL
Merge Files to PDF
Combine multiple documents/images into a single PDF
Download a File
Downloads output from a completed task
Archive File
Creates a ZIP, RAR, 7Z, TAR, TAR.GZ or TAR.BZ2 archive
Optimize File
Creates a task to optimize and compress a file
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported CloudConvert event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Job Event
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported CloudConvert action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Convert File
Combine CloudConvert with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
New Job Event
Finishes with
Convert File, then preserve the outcome in Coherence
The exact authentication fields depend on CloudConvert. The workflow structure stays straightforward:
Authorize the CloudConvert account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with CloudConvert or provide a complementary trigger or action.
CloudConvert currently provides 3 triggers that can start a workflow and 7 actions a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
CloudConvert currently lists 3 triggers and 7 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported CloudConvert triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
