Resources · Make integration

Zamzar Make integrationAutomate Zamzar with Make.

Tired of converting files by hand, one upload at a time? The Zamzar Make integration gives you 10 modules, including 2 triggers, to upload, convert and download files inside an automation. This guide shows what each one does, how to connect your API key and how to build a first working flow.

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, a visual tool where you build a scenario: an automation made of modules, each one a brick that triggers, acts or searches. With it, file conversions start, finish and move on to the next step without you opening Zamzar at all.

Converted files that land where your team works. An operations lead can pair Watch Completed Conversion Jobs with Download a File, then pass the result to a module from another app, so finished files reach the shared drive without anyone checking Zamzar.

Conversions that start from incoming documents. When a file arrives from a form or an inbox handled by another app, Convert a File sends it straight to the format you selected. For a file already stored in Zamzar, Convert an Existing File does the same job without a second upload.

A tidy Zamzar account. List Files returns what sits in your account, and Delete a File removes what you no longer need once the output has been saved elsewhere.

What Make does not do here: both triggers are scheduled, so Make checks Zamzar on the scenario's schedule instead of reacting the second a job ends. For anything the 10 modules leave out, Make an API Call reaches the Zamzar API with the same connection. The same app often has an n8n node too; the n8n vs Make comparison helps you weigh the two, and the Make pricing page covers plans. If a run fails, start with Make troubleshooting.

Connect

How do you connect Zamzar to Make?

  1. 01

    Copy your Zamzar API key

    You need a Zamzar account and an API key before anything else. Log in to the Zamzar developer portal, open the user menu, go to the key management section and copy the API key shown on screen.

  2. 02

    Add a Zamzar module in Make

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear label helps when you run several accounts. Paste the API key you copied, or follow the on-screen instructions, and save.

First scenario

Build your first scenario with Zamzar

GoalWhen a conversion job completes in Zamzar, Make downloads the converted file so the next module can store or send it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. Everything you build next hangs off this starting point.

  2. 02

    Add the trigger

    Search for Zamzar and choose Watch Completed Conversion Jobs. Click Create a connection if you have not linked your API key yet, then fill in the module fields.

  3. 03

    Download the result

    Click the + on the right of the trigger and add Download a File. Map the file from the job the trigger returned, so each finished conversion becomes a bundle, one file passed to the next module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, which tells you whether the download picked up the right file.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Pick your schedule, then switch the scenario on.

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.”

Starts your scenario once Zamzar has finished a conversion job, so the output can move on without you refreshing a dashboard. Each completed job comes through as a bundle the next modules can use.

How it fires
scheduled. Make checks Zamzar on the scenario's schedule, every 15 minutes by default, and picks up the jobs completed since the last check.
When to use it
you launch conversions from another scenario and want a second one to collect and deliver the results.
Watch out
the job is done, but the file still sits in Zamzar. Add Download a File if you need its content.
Zamzar2Watch Files

Watch Files

Scheduled trigger

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

Fires when new files are created in your Zamzar account, which gives you a starting point for anything that should happen right after an upload. Every new file arrives as its own bundle.

How it fires
scheduled. Make polls Zamzar at the interval set on the scenario, not the moment a file appears.
When to use it
files reach Zamzar through different routes and you want one scenario that reacts to all of them, for example by launching Convert an Existing File.
Watch out
if your own scenario uploads files with Upload a File, this trigger will see those too, so check you are not converting the same file twice.
Modules

What can Zamzar do inside a scenario?

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.”

Turns a file coming from an earlier module into the format you select. Pick it when the file is not in your Zamzar account yet.

When to use it
a document arrives from another app, like an email attachment or a form upload, and you need it in a different format before sending it on.
Watch out
each run counts as an operation, one execution of a module that Make bills on your plan.
Zamzar2

Convert an Existing File

Action

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

Converts a file that already lives in your Zamzar account, so you can reuse something uploaded earlier instead of sending it again.

When to use it
right after Watch Files or Upload a File, when the source is already stored in Zamzar and you only need a new output format.
Watch out
the module needs the file to exist in Zamzar; map it from the previous module rather than typing it.
Zamzar3

Delete a File

Action

In Make“Deletes an existing file.”

Removes a file from your Zamzar account, which keeps the storage clean once a conversion has been downloaded and filed elsewhere.

When to use it
at the very end of a scenario, after the converted output has reached its final destination.
Watch out
a deletion cannot be undone from the scenario, so place this module only after a step that confirms the file was saved.
Zamzar4

Download a File

Action

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

Pulls the content of a file out of Zamzar, whether it is the original you uploaded or the converted result, so later modules can store or send it.

When to use it
after Watch Completed Conversion Jobs or Get a Job, when the next module in another app expects the actual file, not just its details.
Watch out
on the Free plan, Make handles files up to 5 MB, so larger outputs call for a paid plan.
Zamzar5

Get a Job

Action

In Make“Returns information about the selected job.”

Returns the details of one conversion job you select, which tells your scenario where that job stands and what it produced.

When to use it
you started a conversion earlier in the flow and want to read its information before deciding whether to download the result.
Watch out
it reads a single job; to react to every finished job, the Watch Completed Conversion Jobs trigger fits better.
Zamzar6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any part of the Zamzar API from your scenario, reusing the connection you already created, so nothing is out of reach when the listed modules stop short.

When to use it
you need a Zamzar feature that none of the other nine modules covers.
Watch out
you write the request yourself, so keep the Zamzar API documentation open next to the editor.
Zamzar7

Upload a File

Action

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

Sends a new file into your Zamzar account so it can serve as input for a later conversion job, keeping upload and conversion as two separate steps.

When to use it
you want to store the source once and convert it several ways with Convert an Existing File.
Watch out
if Watch Files runs on the same account, it will also pick up what this module uploads.
Zamzar8

List Files

Search

In Make“Lists all files.”

Gives you every file stored in your Zamzar account, each one returned as a separate bundle the following modules can process one by one.

When to use it
you are cleaning up the account and want to feed each file into Delete a File.
Watch out
as a search, it can return zero, one or many bundles, and every module after it runs once per file, which adds operations quickly.
Need help

Need help automating Zamzar with Make?

A person reads every message.

FAQ

Zamzar Make integration: common questions

01Is the Zamzar Make integration free?
Yes, on the Make side. Zamzar is a standard app, available 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) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Zamzar itself needs its own account and API key, with its own subscription, which you check on the Zamzar pricing page.
02What do you need to connect Zamzar to Make?
A Zamzar account and an API key. You find the key in the Zamzar developer portal: open the user menu, go to the key management section and copy the key. In Make, add any Zamzar module, click Create a connection, optionally fill in the Connection name field, then paste the key or follow the on-screen instructions. The connection is created once and every Zamzar module in your scenarios reuses it, so you never paste the key twice.
03Does the Zamzar Make integration react in real time?
No. Both Zamzar triggers, Watch Completed Conversion Jobs and Watch Files, are scheduled. Make checks Zamzar on the scenario's schedule and collects what happened since the last check. A new scenario runs every 15 minutes by default. The Free plan keeps that 15 minute minimum, while paid plans let you go down to 1 minute. If you need a faster reaction, the gap between two checks is the setting to change, not the trigger itself.
04What if a Zamzar module is missing in Make?
Use Make an API Call. It sends any request to the Zamzar API with the connection you already set up, which covers whatever the 10 listed modules leave out. You write the request yourself, so the Zamzar API documentation becomes your reference. Keep in mind that the Make documentation for this app is AI-generated from the official Zamzar documentation and may contain mistakes, so verify important details directly with Zamzar before you rely on them.
05Should you use Make or n8n for Zamzar?
It depends on the tool your team already uses. Zamzar often has an n8n node as well as its Make app, so the choice rarely comes down to the app itself. In Make you get 10 ready-made modules, 2 scheduled triggers and Make an API Call for the rest, all built in a visual editor. The practical question is where your other automations already run: keeping file conversion in the same tool keeps connections and troubleshooting in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations