Resources · Zapier integration

CloudConvert Zapier integrationAutomate CloudConvert with Zapier.

The CloudConvert Zapier integration gives you 3 triggers and 6 actions to convert, merge, compress, watermark or archive files, and capture web pages, without opening CloudConvert. Here is what each one does, what it costs, and where it breaks.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the CloudConvert Zapier integration actually does

CloudConvert turns a file from one format into another, across more than 200 formats. Plugged into Zapier, it does that work inside an automation: a file shows up somewhere, CloudConvert processes it, and the result moves on to the next tool. Nobody downloads, converts and re-uploads by hand anymore.

Three results come up first. A PDF pipeline: Convert a File turns incoming Word or image files into PDFs before they are filed. A single document out of many: Merge Files to PDF stitches several attachments into one PDF a client can actually read. Lighter files: Optimize a File shrinks a PDF or image before it goes out by email or into storage. On the other side, Job Failed warns you the moment a conversion breaks, instead of a client telling you.

What Zapier does not do for CloudConvert is just as useful to know. There is no search step, so a Zap cannot look up an old job and reuse it. Every action needs a file, or a list of files, handed over by an earlier step, as a file object, a text or a link: the file fields take nothing else. And the triggers report jobs (created, failed, finished), nothing more.

Before you commit, compare with the CloudConvert n8n integration and the CloudConvert Make integration.

Vocabulary

Zapier vocabulary in one minute

Six words come back all over this page. Here they are, without jargon.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap. With CloudConvert, that is a job being created, failing or finishing.
Action
What the Zap does once it has started: the step that writes, sends or moves something, here a conversion or a merge.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan is counted in those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant one is reported by the app. All CloudConvert triggers are instant.
Filter
A step that lets the Zap go on only when the incoming data meets your condition, and stops it quietly otherwise.
Cost

What a CloudConvert Zap really costs

CloudConvert is not a premium app, so it runs from the free Zapier plan.

  • Free plan100 tasks a month
  • Zaps on freeTwo steps only
  • Premium appNo
  • Trigger speedInstant on every plan

On the Zapier side, the trigger never costs a task. Each action that succeeds costs one, so a Zap that converts then merges spends two per run. A failed action is not counted. The free plan gives 100 tasks a month, in Zaps of two steps: one trigger, one action. A second action or a filter makes the Zap multi-step, and that needs a paid plan. The polling grid below does not apply here: the three CloudConvert triggers are instant on every plan.

Connect

Connect CloudConvert to Zapier in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your CloudConvert account linked to Zapier once, then reused by every step that calls CloudConvert.

  2. 02

    Pick CloudConvert

    Search CloudConvert in the dialog, select it and click Add connection. CloudConvert then opens in a new tab, where the next step happens: keep the Zapier window open behind it until the connection is saved.

  3. 03

    Sign in and grant access

    Log in to your CloudConvert account in that tab and allow Zapier to use it. You need a CloudConvert account for this, so create one first if the team has none.

First Zap

Your first Zap: file every finished job

GoalEach time a CloudConvert job finishes, keep only the ones that matter and upload the result to a shared folder.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose CloudConvert and Job Finished as the event, then select your connection. There is no interval to set: CloudConvert reports each finished job itself.

  2. 02

    Test the trigger on a real job

    Run the test. Zapier brings back the three most recent finished jobs of the account, so run one conversion in CloudConvert first if the list is empty.

  3. 03

    Add a filter

    Add a Filter step, then set the field to look at, the rule and the value. Text rules only work on text, so pick the rule type that matches the field.

  4. 04

    Add the upload

    Add the storage app of your choice and its upload action, then map the output file of the job into its file field. Name the folder where results should land.

  5. 05

    Test, then publish

    Test each step and read what came back. With a filter, this Zap is multi-step and needs a paid plan. When it looks right, click Publish.

Triggers

CloudConvert triggers on Zapier

3 events start a Zap when something happens in CloudConvert, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Job

Instant trigger

In Zapier“Triggers when a new job is created.”

Starts your Zap as soon as a new job is created in CloudConvert, before anyone knows whether it will finish or fail.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you keep a log of every conversion requested, for usage tracking or to see who sends what.
Watch out
the CloudConvert actions create jobs too, so a Zap started here that runs one of them can set itself off again.
2

Job Failed

Instant trigger

In Zapier“Triggers when a job failed.”

Your alarm bell. It fires when a job could not complete, so you hear about a broken conversion before the person waiting for the file does.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a client portal sends files for conversion and someone on the team must step in whenever one fails.
Watch out
do not answer a failure by relaunching the same conversion automatically; pass it to a person who can look at the file.
3

Job Finished

Instant trigger

In Zapier“Triggers when a job finished.”

Fires when a job completes successfully, which is the moment the converted, merged or compressed file actually exists. This is where the result leaves CloudConvert for storage, email or a client folder.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every finished job should land in the right folder without anyone downloading it.
Watch out
it fires for every finished job, whatever started it; a filter keeps only the ones you want.
Actions

CloudConvert actions on Zapier

CloudConvert gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Watermark to a File

Action

In Zapier“Add a watermark to a PDF file, to an image or to a video.”

Stamps a watermark on a PDF, an image or a video handed over by an earlier step.

When to use it
drafts, proofs or previews leave the company and must be marked as such before anyone sees them.
Watch out
the File field is required and must come from another step, as a file object, a text or a link.
2

Create Archive

Action

In Zapier“Create a ZIP, RAR... archive.”

Packs several files into a single archive, ZIP or RAR for instance, in the format you choose.

When to use it
a delivery made of many files should reach the client as one download instead of a dozen attachments.
Watch out
both Files and Output Format are required; without the format, the step does not know what to build.
3

Capture a Website

Action

In Zapier“Creates job to capture a website as PDF or create a website screenshot as JPG or PNG.”

Opens a web address and saves it as a PDF, or as a JPG or PNG screenshot. It is the only action that starts from a web page instead of a file.

When to use it
you archive a page as it looked on the day a form was sent, or keep proof of a published offer.
Watch out
the URL and the output format are both required.
4

Convert a File

Action

In Zapier“Creates job to convert a file.”

The workhorse, and the action Zapier puts forward for this app: it takes one file and returns it in the format you name.

When to use it
Word documents, scans or images arrive by email or form and must be stored as PDFs.
Watch out
File and Output Format are required, and the file has to come from an earlier step, not from your CloudConvert account.
5

Merge Files to PDF

Action

In Zapier“Merge multiple files into one single PDF.”

Combines several files into one single PDF, so the reader opens one document.

When to use it
a quote, its terms and its appendix go out as one document rather than three.
Watch out
it needs Files, plural, from earlier steps, plus the output format; a single file gives you nothing to merge.
6

Optimize a File

Action

In Zapier“Creates job to optimize a file.”

Makes a file lighter, which helps when a PDF or an image is too heavy to send or store comfortably.

When to use it
scanned contracts or photo-heavy reports go out by email and are heavier than they need to be.
Watch out
the File field is required, and it has to come from an earlier step, not from your CloudConvert account.
When it breaks

When a CloudConvert Zap breaks

Zapier attaches no help article to CloudConvert and no CloudConvert-specific limit is documented here. What breaks is Zapier's own mechanics, and with an app that both creates and reports jobs, one of them bites harder than usual.

Read the Zap history first: a step that did not run, or ran far too often, usually points to one of the cases below. The Zapier troubleshooting guide covers what is left.

  • The Zap feeds itself

    The actions create CloudConvert jobs, and the triggers watch jobs. A Zap that starts on a job and runs a CloudConvert action can set itself off again and burn tasks fast.

  • Older files are never processed

    A Zap only reacts to what happens after you publish it. Jobs and files from before stay untouched; converting a backlog is a separate job.

  • A big batch gets held back

    When a trigger suddenly returns a huge batch, after a bulk upload for instance, Zapier's flood protection can hold it back before any action runs.

  • No file, no conversion

    If the earlier step hands over an empty field instead of a file, a text or a link, the action has nothing to work on and the run fails.
Need help

Need help automating CloudConvert with Zapier?

A person reads every message.

FAQ

CloudConvert Zapier integration: common questions

01Is the CloudConvert Zapier integration free?
On the Zapier side, yes, within limits. CloudConvert is not a premium app, so the free plan accepts it, with 100 tasks a month. The free plan only builds two-step Zaps, one trigger and one action. A Zap that converts then merges, or that carries a filter, is multi-step and needs a paid plan. The three triggers stay instant on the free plan too, so speed does not depend on what you pay.
02How many Zapier tasks does a CloudConvert Zap use?
One per action that succeeds, and none for the trigger. A Zap that converts each new file spends one task per file. If it converts and then optimizes, that is two per run. A failed conversion costs no Zapier task. Watch the loop case: a Zap that creates jobs on a job trigger keeps setting itself off, and each round spends another task until you switch it off. The trigger side stays free, however many jobs CloudConvert reports.
03Do CloudConvert triggers work in real time?
Yes. All three CloudConvert triggers are instant: CloudConvert tells Zapier itself when a job is created, fails or finishes, so the Zap starts straight away. The interval grid of Zapier plans, every 15 minutes on the free one, only concerns polling triggers and does not slow these down. That is good news on a free plan, and the editor shows a lightning bolt on such Zaps. Nothing to tune, nothing to upgrade for speed.
04What does it take to connect CloudConvert to Zapier?
A CloudConvert account and a Zapier account. From the Apps page of Zapier, add a connection, sign in to CloudConvert in the tab that opens and grant access. Jobs started by your Zaps then run in that account, so choose the one your team uses. For the actions, plan an earlier step that hands over a real file, a text or a link: that is the field every action requires.
05Why does a CloudConvert Zap keep running on its own?
Because it probably feeds itself. The CloudConvert actions create jobs (Convert a File, for instance, creates a job to convert), and New Job fires whenever a new job is created. If your Zap starts on a job trigger and runs a CloudConvert action, it writes into the very place its trigger watches, and each run can start it again. Turn it off, then add a filter that only lets through the jobs you care about, or start the Zap from the app where the files come from.
06What if the CloudConvert action you need does not exist on Zapier?
Then the catalog does not offer it and no setting will add it. Zapier lists 6 actions for CloudConvert: watermark, archive, website capture, conversion, merge to PDF and optimization, and no search step at all. For anything else, look at other platforms: CloudConvert is also on Make and n8n with their own catalogs, worth comparing before you build a workaround. Start with the operation that matters most to your process, and check both catalogs for it.
07Zapier, Make or n8n for CloudConvert?
It depends on your criteria, not on a winner. Zapier is quick to set up, its CloudConvert triggers are instant and work on the free plan, but a Zap that chains several file steps needs a paid plan. For Make and n8n, look at their own CloudConvert pages: compare the operations each one offers against the steps your file flow really needs, and the tool your team already uses. The right pick is the one that covers your case without a workaround.
Same platform

Other docs you might need on this stack.

Browse all integrations