Resources · Make integration

Zuora Make integrationAutomate Zuora with Make.

Can Make push usage into Zuora and pull invoices back out without a line of code? The Zuora Make integration offers 24 modules: 20 actions and 4 searches. This guide is for billing and ops teams; it walks you through the connection, a first scenario and every module.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Zuora integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Zuora Make integration let you automate?

The Zuora Make integration links your Zuora account to Make, a visual tool where you build a scenario (the automation itself: a chain of modules, each one a brick that reads or writes data). Once connected, Make can create usage records, run billing previews, query your data and fetch invoice PDFs for you.

Usage that bills itself. Your product logs consumption somewhere else, in a database or a spreadsheet. A scenario reads each new line and sends it through Create a Usage Record (Advanced), so the numbers finance bills on are the ones your product measured.

Invoices where people look for them. With List All Files of an Invoice and Download an Invoice File, the PDF of an invoice can travel to a shared drive, a customer portal or an email, without anyone exporting it by hand.

Pricing changes you can check before they hit. Update a Product Rate Plan Charge Tier Price applies a new price, and Perform a Billing Preview Run shows the invoice items Zuora plans to produce, so you spot a surprise before customers do.

Know the limits before you start. Zuora has no trigger in Make, so a scenario starts on its schedule or on another app's event. Several modules marked Advanced expect a JSON payload you write yourself, and Zuora is an enterprise app, available on the Make Enterprise plan only; see Make pricing for how plans compare. If you are weighing tools, n8n vs Make sets out the differences, and Make training helps you get fluent with the editor.

Connect

How do you connect your Zuora account to Make?

  1. 01

    Create an OAuth client in Zuora

    Log in to Zuora and create an OAuth Client. Zuora then shows a Client ID and a Client Secret: copy both and keep them somewhere safe, because Make will ask for them in the next step.

  2. 02

    Add a Zuora module and open the connection form

    In Make, add any Zuora module to your scenario and click Create a connection. A connection is your Zuora account linked to Make once, then reused by every Zuora module. You can name it in Connection name.

  3. 03

    Fill in the region and credentials, then save

    In Region, type only the region part of your Zuora URL. Paste the Client ID and Client Secret in their fields and click Save. If Zuora asks you to authenticate and confirm access, accept.

First scenario

Your first scenario: send usage from another app into Zuora

GoalWhen another app records new customer usage, Make creates the matching usage record in Zuora.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Since Zuora has no trigger, the first module comes from the app where your usage lands, a sheet or a database.

  2. 02

    Set up the source module

    Pick the module of that app that returns new rows, connect its account and fill its fields. Each row it returns becomes a bundle: one item that flows to the next module.

  3. 03

    Add Create a Usage Record (Advanced)

    Click the + on the right of the first module, search for Zuora and choose Create a Usage Record (Advanced). Pick the connection you made earlier, or click Add to create it.

  4. 04

    Map the usage into the JSON payload

    Write the JSON body the module expects, following the Zuora API documentation, and drop into it the values the previous module returned for each row of usage.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received. Check in Zuora that the usage record appears as expected.

  6. 06

    Schedule and switch it on

    Open the clock on the first module to set the schedule (every 15 minutes by default), then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What can each Zuora module do in Make?

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

Zuora1

Create a Billing Preview Run (Advanced)

Action

In Make“Creates a billing preview run for multiple customer accounts. Use the Perform a Billing Preview Run module to create and retrieve a billing preview run all in one module.”

Launches a billing preview covering several customer accounts at once, so you can later see what Zuora is about to invoice them. This module starts the run and stops there.

When to use it
a large preview that may need longer than the wait built into Perform a Billing Preview Run.
Watch out
reading the result is a separate job, handled by Retrieve a Billing Preview Run (Advanced) further down the scenario.
Zuora2

Create a Product Rate Plan (Advanced)

Action

In Make“Create a product rate plan with custom JSON payload.”

Adds a new product rate plan to your Zuora catalog from a JSON payload you write. You decide exactly what goes into the plan, in exchange for building the body yourself.

When to use it
a new offer was drafted in a pricing sheet and should reach Zuora without anyone retyping it.
Watch out
Make does not assemble the payload for you, so check the expected structure in the Zuora API documentation before the first test.
Zuora3

Create a Product Rate Plan Charge (Advanced)

Action

In Make“Create a product rate plan charge for a specified rate plan using a custom JSON payload.”

Attaches a charge to a rate plan you name, again through a custom JSON payload. The plan has to exist already, which is why this module often follows Create a Product Rate Plan (Advanced).

When to use it
a freshly created plan still needs its recurring fee or its usage price.
Watch out
map the plan from the previous module instead of typing it, or every run will write to the same plan.
Zuora4

Create a Usage Record (Advanced)

Action

In Make“Create a usage record with a JSON payload.”

Records consumption in Zuora, so usage based charges reflect what customers really used. Each bundle you send becomes one usage record, described in JSON.

When to use it
your product or a spreadsheet logs usage, and finance wants it in Zuora without a manual import.
Watch out
one bundle means one record and one operation, so filter out test rows before switching the scenario on.
Zuora5

Describe an Object

Action

In Make“Get all the information and fields from a Zuora object.”

Gives you the full picture of a Zuora object: its information and every field it carries. Treat it as the map you read before writing a payload or a query against that object.

When to use it
you are building on an object you do not know by heart and need its exact field names.
Watch out
it only reads; once the scenario works, remove it if you no longer need that information on every run.
Zuora6

Download an Invoice File

Action

In Make“Download the most current invoice as a PDF.”

Hands the next module the most current version of an invoice as a PDF, ready to attach to an email or save in a shared folder.

When to use it
a customer asks for a copy, or accounting keeps every invoice in its own storage.
Watch out
you get the latest version only; to see every PDF stored for the same invoice, run List All Files of an Invoice first.
Zuora7

Get a Product Rate Plan Charge

Action

In Make“Retrieve a product rate plan charge by id.”

Reads a single product rate plan charge from its ID and exposes its details to the modules that follow. Nothing in Zuora changes.

When to use it
before updating a charge, to see what it holds now, or to copy it into a pricing review sheet.
Watch out
it needs the exact ID; when you only know the product, find the charge first with one of the ZOQL query modules.
Zuora8

List All Custom Fields for an Object

Action

In Make“Retrieve the custom fields of a specific object.”

Returns the custom fields defined on one Zuora object, the ones your admins added on top of what Zuora ships with.

When to use it
your payloads or queries must fill company specific fields, and you want their names spelled exactly as Zuora stores them.
Watch out
when you also need the standard fields, Describe an Object is the module that returns everything about the object.
Zuora9

Make an API Call

Action

In Make“Make an arbitrary authorized API call.”

Opens the rest of the Zuora API to your scenario, using the connection you already set up. Any endpoint the other modules leave aside can be reached here.

When to use it
you need a Zuora operation that none of the listed modules offers.
Watch out
you write the request yourself, path and body included, so keep the Zuora API documentation open for the endpoint you target.
Zuora10

Perform a Billing Preview Run

Action

In Make“Creates and retrieves a billing preview run. The maximum amount of time this module will check for the preview run to be complete is 6 mins, for larger runs use the Billing Preview Run (Advanced) modules.”

Creates a billing preview and brings its result back in the same module, so you see the upcoming invoice items of several accounts without chaining two steps.

When to use it
checking what customers will be billed after a price change, on a preview of reasonable size.
Watch out
the module waits 6 minutes at most for the run to finish; for bigger runs, switch to the two Billing Preview Run (Advanced) modules.
Zuora11

Perform a Data Query

Action

In Make“Submits and retrieves a data query performed by Zuora.”

Sends a data query to Zuora and returns its result once Zuora has processed it, all inside one module and one run of the scenario.

When to use it
extracting a set of records for a report or a sync, when the answer should arrive in the same run.
Watch out
if you prefer to submit now and read later, use the pair Submit a Data Query (Advanced) and Retrieve a Data Query (Advanced) instead.
Zuora12

Retrieve a Billing Preview Run (Advanced)

Action

In Make“Retrieves a preview of future invoice items for multiple customer accounts through a billing preview run.”

Fetches the result of a billing preview run launched earlier: the future invoice items of every account it covered.

When to use it
as the second half of the Advanced pair, after Create a Billing Preview Run (Advanced) has started the run.
Watch out
the module reads a run that already exists, so map its reference from the create module rather than typing it by hand.
Zuora13

Retrieve a Bill Run

Action

In Make“Retrieves the information about a specific bill run.”

Pulls the details of one specific bill run into the scenario, so the next module can report on it or pass it along.

When to use it
finance wants a message in the team chat, or a line in a tracking sheet, about a given bill run.
Watch out
it targets one bill run you point to; it is not a way to browse all of them.
Zuora14

Retrieve a Data Query (Advanced)

Action

In Make“Retrieves a data query job.”

Collects a data query job created earlier, so the rest of the scenario can work with what Zuora prepared.

When to use it
heavy queries you would rather launch with Submit a Data Query (Advanced) and read in a later step or a later run.
Watch out
it only makes sense once a job exists; map the job from the submit module so both point to the same query.
Zuora15

Retrieve a File

Action

In Make“Retrieve files such as export results, invoices, and accounting period reports.”

Brings a file out of Zuora, such as an export result, an invoice or an accounting period report, and hands it to the next module.

When to use it
the accounting period report has to land in the finance drive without anyone downloading it.
Watch out
for a plain invoice PDF, Download an Invoice File is the more direct module; keep this one for exports and reports.
Zuora16

Run a Workflow

Action

In Make“Run a specified workflow.”

Starts a workflow you already built inside Zuora. The logic stays in Zuora; Make only decides the moment it runs.

When to use it
an event in another app, such as a contract signed in your CRM, should set a Zuora workflow in motion.
Watch out
Make runs the workflow you name and nothing more, so test that workflow in Zuora before wiring it to a scenario.
Zuora17

Submit a Data Query (Advanced)

Action

In Make“Submits a data query to be performed by Zuora and creates a query job.”

Hands a data query to Zuora and creates a query job, without waiting for the answer. The scenario can move on straight away.

When to use it
large extractions you want to start now and collect later with Retrieve a Data Query (Advanced).
Watch out
on its own this module only creates the job; without the retrieve module, you never see the records it gathered.
Zuora18

Update a Product Rate Plan Charge (Advanced)

Action

In Make“Updates the information about a product rate plan charge with a custom JSON payload.”

Modifies an existing product rate plan charge through a custom JSON payload, which covers changes the simpler modules cannot make.

When to use it
a charge needs more than a new price, and the change touches parts of the charge the tier price module leaves alone.
Watch out
read the charge first with Get a Product Rate Plan Charge, so you know exactly what you are about to overwrite.
Zuora19

Update a Product Rate Plan Charge Tier Price

Action

In Make“Updates the price of a product rate plan charge tier. To make other updates to product rate plan charge tiers, use Update a Product Rate Plan Charge.”

Changes the price of one tier of a charge, and only that. It is the shortest path to a new price, with no JSON to write.

When to use it
a new price list was approved in a sheet and each row should update the matching tier.
Watch out
any other change to a tier goes through Update a Product Rate Plan Charge (Advanced), not through this module.
Zuora20

Update a Usage Record (Advanced)

Action

In Make“Updates a usage record with a JSON payload.”

Corrects a usage record already in Zuora through a JSON payload, so billing follows the fixed figure rather than the wrong one.

When to use it
your product sends a correction after the fact, for example a quantity recalculated after an incident.
Watch out
you must target the right record; keep its reference from the scenario that created it, or find it with a ZOQL query.
Zuora21

List All Files of an Invoice

Search

In Make“Retrieves the information about all PDF files of a specified invoice.”

Returns information about every PDF file stored for one invoice, each file as its own bundle. It is a search, so it may return zero, one or several results.

When to use it
you need an older version of an invoice, or want to archive every PDF of it.
Watch out
the modules placed after it run once per file, and each run counts as an operation.
Zuora22

Run a ZOQL Query

Search

In Make“Run a ZOQL query with preconfigured syntax.”

Pulls records out of Zuora with a ZOQL query whose syntax the module prepares for you, a gentle way in if you have never written one.

When to use it
finding the accounts or charges a scenario should work on before an update or an export.
Watch out
the directory describes this module and Run a ZOQL Query (Select) the same way; try both on a small query and keep the one that fits.
Zuora23

Run a ZOQL Query (Advanced)

Search

In Make“Run a ZOQL query with full control of syntax.”

Lets you write the whole ZOQL query yourself, with full control over its syntax, and returns each matching record as a bundle.

When to use it
the prepared syntax of the other query modules cannot express the filter you need.
Watch out
every returned record triggers the modules that follow, so test with a narrow query before you run it on your whole Zuora account.
Zuora24

Run a ZOQL Query (Select)

Search

In Make“Run a ZOQL query with preconfigured syntax.”

Another ZOQL search with a preconfigured syntax, listed in Make under its own name, that returns the matching Zuora records one bundle at a time.

When to use it
a quick lookup, such as the invoices of one account, before you pass them to Download an Invoice File.
Watch out
its description matches Run a ZOQL Query word for word, so compare their fields in the editor before choosing.
Need help

Need help automating Zuora with Make?

A person reads every message.

FAQ

Zuora and Make: frequently asked questions

01Is the Zuora Make integration free?
No. Zuora is an enterprise app in Make, and enterprise apps are reserved for the Enterprise plan. The Free plan lets you try Make itself with 2 active scenarios, a 15 minute minimum between scheduled runs and files up to 5 MB, but its 3,000+ standard apps do not include Zuora. Paid plans (Core, Pro, Teams and Enterprise) count usage in credits, one operation per module run on a bundle, so budget for the Enterprise plan before you design a Zuora scenario.
02What do you need to connect Zuora to Make?
You need a Zuora account where you can create an OAuth client, since that client gives you the Client ID and Client Secret Make asks for. In Make, you add a Zuora module, click Create a connection, type your region, paste both values and save. The region is the part of your Zuora URL placed before .zuora.com, not the whole address. If Zuora then asks you to authenticate and confirm access, accept, and the connection is ready for every Zuora module.
03Can the Zuora Make integration react in real time?
No, because Zuora has no trigger module in Make, neither scheduled nor instant. A scenario that uses Zuora starts in one of two ways. Either it runs on its schedule, set with the clock on the first module, every 15 minutes by default and down to 1 minute on paid plans. Or it opens on a trigger from another app, such as a new row or a new contract, and the Zuora modules come after it. Pick the second option when the event lives outside Zuora.
04What if a Zuora module you need is missing in Make?
Use Make an API Call. This module is part of the Zuora app in Make and reaches any endpoint of the Zuora API with the connection you already created, so nothing new to authorize. You write the request yourself, which means keeping the Zuora API documentation at hand. The Zuora documentation in Make gives no numeric limit for these modules, so the practical limits come from your Make plan: execution time, operations and schedule interval.
05Should you use Make or n8n for Zuora?
It depends on what your team already runs. On Make, Zuora comes with 24 modules, including Make an API Call for everything else, and it requires the Enterprise plan. The same app often has a node in n8n too, so check what that node covers before deciding. The fairest test is practical: rebuild one small flow, such as a usage record created from a sheet, in each tool and keep the one your team maintains with less effort.
Same platform

Other docs you might need on this stack.

Browse all integrations