Resources · Make integration

Zamzar Make integrationAutomate Zamzar with Make.

What if every file conversion ran without you touching it? The Zamzar Make integration gives you 10 modules: 2 triggers, 7 actions and 1 search. This page is for anyone who converts files by hand today, and it walks you through your first working scenario.

Try the Zamzar integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Zamzar Make integration do for you?

The Zamzar Make integration links your Zamzar account to Make, so a scenario (the automation you build in Make, a chain of small steps) can upload a file, convert it to another format, fetch the result and clean up afterwards. You set it up once with clicks, not code.

Clean deliverables for clients. A designer drops a source file in shared storage, another app hands it to Make, Upload a File sends it to Zamzar and Convert an Existing File turns it into the format the client asked for.

Results that come back on their own. Watch Completed Conversion Jobs notices each finished job, then Download a File pulls the converted copy so the next module can store or email it.

A tidy account. List Files shows what sits in Zamzar and Delete a File removes what you no longer need.

Know the edges before you start. The documentation gives no numeric limit for this app, and anything the 10 modules do not cover goes through Make an API Call, which reuses your connection. If you are still choosing a platform, read our Make review and the n8n vs Make comparison. When a run fails, Make troubleshooting covers the usual causes.

Connect

How do you connect Zamzar to Make?

  1. 01

    Add a Zamzar module

    In a scenario, add any Zamzar module and click Create a connection. A connection is your Zamzar account linked to Make once and reused by every Zamzar module you add later.

  2. 02

    Give the connection a name

    This step is optional, but a clear name such as the team or client it serves helps when you run several accounts. You will pick it from a dropdown in every Zamzar module afterwards.

  3. 03

    Authorize and save

    Authorize Make on the Zamzar page that opens, or paste the key Zamzar gives you, depending on what the window asks for. Then click Save and the module is ready to fill in.

First scenario

Your first scenario with Zamzar

GoalWhen a file lands in another app, Make uploads it to Zamzar and starts its conversion into the format you picked.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module: the app where your files arrive, such as a mailbox or a storage folder.

  2. 02

    Upload the file to Zamzar

    Click the + to the right, search for Zamzar and pick Upload a File. Create the connection, then map the file coming from the first module.

  3. 03

    Start the conversion

    Add Convert an Existing File after the upload, map the file Zamzar just received and choose the target format from the list Make shows you.

  4. 04

    Test with Run once

    Put a sample file in the source app and click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one file.

  5. 05

    Schedule and switch on

    On the first module, set the schedule (every 15 minutes by default) and switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What can start a Zamzar scenario?

2 modules start a scenario when something happens in Zamzar. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Zamzar as soon as it happens.

Zamzar1Watch Completed Conversion Jobs

Watch Completed Conversion Jobs

Scheduled trigger

In Make“Triggers when a conversion job has completed.”

This trigger starts your scenario from Zamzar's finished work: each completed conversion job becomes a bundle your scenario can act on, so you stop checking the account for results.

How it fires
it is a scheduled trigger, meaning Make checks Zamzar on the scenario's schedule and collects the jobs completed since the previous check.
When to use it
pick it when conversions are started elsewhere, by a teammate or another scenario, and you want the output collected with Download a File.
Watch out
pair it with a download step, since a completed job alone does not put the file anywhere.
Zamzar2Watch Files

Watch Files

Scheduled trigger

In Make“Triggers when the new files are created.”

Watch Files lets you react to new material in Zamzar itself: each new file created in your account becomes a bundle and starts a run of your scenario.

How it fires
it is a scheduled trigger, so Make polls your Zamzar account on the scenario's schedule instead of hearing about each file right away.
When to use it
choose it when files reach Zamzar through its own interface and you want Make to take over from there, for example to convert them with Convert an Existing File.
Watch out
the first Run once shows you exactly which files reach the scenario, so check those bundles before you add a Delete a File step.
Modules

What can Make do in Zamzar?

Zamzar gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Zamzar1

Convert a File

Action

In Make“Converts a file to the selected format.”

Convert a File turns the file you hand it into the format you select, so a document from any earlier module leaves the step in the shape your team needs.

When to use it
the file comes straight from another app in the same scenario, such as an attachment, and you only need the converted version.
Watch out
for a file already stored in your Zamzar account, Convert an Existing File is the module built for that case.
Zamzar2

Convert an Existing File

Action

In Make“Converts an existing file to the selected format.”

With this module you convert a file that is already stored in your Zamzar account, picking it and the target format instead of sending new content.

When to use it
right after Upload a File, or after Watch Files spots something new, when the same source needs one or several output formats.
Watch out
the conversion starts a job; use Get a Job or the completed-jobs trigger to know when the result is ready.
Zamzar3

Delete a File

Action

In Make“Deletes an existing file.”

Delete a File keeps your Zamzar account clean by removing a file once your scenario no longer needs it, source or converted output alike.

When to use it
as the last module, after Download a File has stored the result where your team works.
Watch out
a deletion cannot be undone, so test the whole chain with Run once before you place this module at the end.
Zamzar4

Download a File

Action

In Make“Downloads a file (both original files and converted files).”

Download a File brings a file out of Zamzar and into your scenario as data, both originals and converted versions, so the next module can store, attach or share it.

When to use it
right after Watch Completed Conversion Jobs, to send the fresh output to a drive or an email module.
Watch out
this module only fetches the content; add another app's module after it or the file goes nowhere.
Zamzar5

Get a Job

Action

In Make“Returns information about the selected job.”

Get a Job returns the information Zamzar holds about one conversion job you select, so later modules can read it instead of you opening the account.

When to use it
after a conversion started in the same scenario, when you want to read the job before downloading the output.
Watch out
you need the job you want to read, so map it from the conversion module rather than typing it by hand.
Zamzar6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call opens the rest of the Zamzar API to your scenario, reusing the same connection, for anything the nine other modules leave out.

When to use it
you found an endpoint in the Zamzar API documentation that no listed module handles.
Watch out
you write the request yourself, so check the endpoint and its parameters in the API reference before running it.
Zamzar7

Upload a File

Action

In Make“Uploads a new file that can be used as input to a conversion job.”

Upload a File places a new file in your Zamzar account so it can serve as the input of a later conversion job, which splits sending and converting into two clear steps.

When to use it
you plan to convert one source into several formats, or to keep it in Zamzar for later.
Watch out
uploading alone converts nothing; follow it with Convert an Existing File.
Zamzar8

List Files

Search

In Make“Lists all files.”

List Files gives you an inventory of your Zamzar account, returning each file as its own bundle so later modules can handle them one at a time.

When to use it
a cleanup scenario that reviews stored files before Delete a File removes the ones you no longer need.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which adds operations.
Need help

Need help automating Zamzar with Make?

A person reads every message.

FAQ

Zamzar and Make: frequent questions

01Is the Zamzar Make integration free?
Yes, Zamzar is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations each month. Your Zamzar subscription is a separate matter that Make does not cover.
02What do you need to connect Zamzar to Make?
A Zamzar account and a Make account. The Zamzar documentation lists no extra prerequisite and no official connection steps, so the generic Make flow applies: add a Zamzar module, click Create a connection, optionally name it, authorize Make on the Zamzar page or paste the key Zamzar gives you, then click Save. The connection is stored once, and every Zamzar module in all your scenarios can reuse it without asking again.
03Do the Zamzar triggers in Make run in real time?
No. Both Zamzar triggers, Watch Completed Conversion Jobs and Watch Files, are scheduled: Make checks your Zamzar account on the scenario's schedule and picks up whatever happened since the last check. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans can go down to 1 minute. Neither trigger is instant, so there is no webhook from Zamzar to Make for these events.
04What if a Zamzar module is missing in Make?
Use Make an API Call. It is part of the Zamzar app in Make and lets a scenario call any endpoint of the Zamzar API with the connection you already set up, so you are not limited to the 10 listed modules. You build the request yourself from the Zamzar API reference. The Zamzar documentation in Make gives no numeric limit for this app, so the constraints you meet will mostly be those of your Make plan, such as file size or execution time.
05Should you use Make or n8n for Zamzar?
It depends on the tool you already run. Apps like Zamzar often have an n8n node too, so check that side before deciding, and weigh which editor your team knows and where your other automations live. On Make, the Zamzar app brings 10 modules, including Make an API Call for the rest of the API, and it is available from the Free plan. The comparison page linked above goes through the criteria side by side without ranking one over the other.
Same platform

Other docs you might need on this stack.

Browse all integrations