# CloudConvert integrations: jobs

> Create a job, create thumbnails and import files in CloudConvert, and start a workflow when CloudConvert sends “Job created”.

**Canonical page:** https://tray.ai/connectors/cloudconvert-integrations/
**Categories:** Documents and e-signature
**Connects through:** HTTP Connector

## Overview

CloudConvert is a file conversion service that turns documents, images, audio, video, and other files from one format into another through a web app or API. Tray.ai connects to CloudConvert through the HTTP Connector, so your workflows can call the CloudConvert API alongside the rest of your stack.

## Use cases

### Jobs

Read, create, delete, and manage jobs in CloudConvert from any Tray.ai workflow. The CloudConvert API covers calls such as create a job and get a job.

- Create a job
- Get a job
- Wait for a job

### File operations

Create, update, and manage file operations in CloudConvert from any Tray.ai workflow. The CloudConvert API covers calls such as convert files and optimize files.

- Convert files
- Optimize files
- Merge files

### Imports and exports

Read and create imports and exports in CloudConvert from any Tray.ai workflow. The CloudConvert API covers calls such as import files and export files.

- Import files
- Export files

### Webhooks

Read, create, and delete webhooks in CloudConvert from any Tray.ai workflow. The CloudConvert API covers calls such as create a webhook and list webhooks.

- Create a webhook
- List webhooks
- Delete a webhook

### CloudConvert events

Start a Tray.ai workflow the moment something happens in CloudConvert. CloudConvert sends events such as job created and job finished to a Tray.ai webhook trigger.

- Job created
- Job finished
- Job failed

## Challenges Tray.ai solves

### Keeping CloudConvert credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store CloudConvert credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the CloudConvert API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the CloudConvert API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to CloudConvert?

Yes. Tray.ai connects to CloudConvert through the HTTP Connector, which calls the CloudConvert API directly. Any call the CloudConvert API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with CloudConvert?

The CloudConvert API uses a bearer token and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated CloudConvert connector?

CloudConvert runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated CloudConvert connector from the CloudConvert API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/