Resources · Make integration

ReviewStudio Make integrationAutomate ReviewStudio with Make.

Tired of copying clients and projects into ReviewStudio by hand? The ReviewStudio Make integration gives you 20 modules: 4 triggers, 13 actions and 3 searches. This page is for the people who run creative review. It shows you how to link your account and build a first scenario.

Try the ReviewStudio integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the ReviewStudio Make integration do?

The ReviewStudio Make integration links your ReviewStudio account to Make, a no-code tool where you build a scenario, meaning an automation made of modules chained together. Each module is one brick: a trigger that starts things, an action that changes something, or a search that finds records. With it, clients, projects, reviews and approval decisions move without a single copy and paste.

Approvals that reach the rest of your stack. Watch New Approval Decisions collects each new decision at every check, so the next step can start: close a task elsewhere, or call Update a Project to move the job along. Nobody has to refresh the review screen to find out.

A project ready as soon as a client exists. Pair Watch New Clients with Create a Project and every new client gets a workspace without anyone thinking about it. The Make review explains how the editor handles this kind of chain.

A clean register of reviews. List Reviews returns every review it finds, one bundle each, which you can push to a sheet or a report for the account team. Get a Review pulls a single one when you already hold its ID.

What Make will not do for you: there are no instant triggers here. Make's doc gives no type for the 4 triggers; their Watch names point to scheduled triggers, so Make checks ReviewStudio on the scenario's schedule. If a job is missing from the listed modules, Make an API Call reaches the rest of the ReviewStudio API with the same connection. The Make pricing page covers what each plan allows, and if you are weighing tools, n8n vs Make lays out the criteria side by side.

Connect

How do you connect ReviewStudio to Make?

  1. 01

    Copy your API key

    In ReviewStudio, open the Settings section from the main menu, click the Configuration tab, and copy the value in the API key field. You need an active ReviewStudio account for this key to exist.

  2. 02

    Add a ReviewStudio module

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

  3. 03

    Name it and paste the key

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the API key you copied, confirm, and Make can now read your clients, projects and reviews.

First scenario

Your first scenario: a project for every new client

GoalWhen a new client appears in ReviewStudio, Make creates a project for that client.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add your first module. The canvas stays empty until you pick one.

  2. 02

    Add Watch New Clients

    Search for ReviewStudio, choose Watch New Clients and click Create a connection with your API key. Fill the fields Make shows; it lists what it can read once the connection works.

  3. 03

    Chain Create a Project

    Click the + on the right of the trigger and add Create a Project. Map data from the client bundle into its fields, so each project carries the right client from the start.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received. Check that the project appeared in ReviewStudio before going further.

  5. 05

    Schedule and switch it on

    Open Scheduling on the first module. A new scenario runs every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

What can start a ReviewStudio scenario?

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

ReviewStudio1Watch New Approval Decisions

Watch New Approval Decisions

triggerIn the docs only

Sends each new approval decision into your scenario, so a sign-off or a rejection can set off the next step without anyone watching the review screen.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and collects the decisions made since the last check.
When to use it
when an approved creative should close a task, alert a producer or update the project it belongs to.
Watch out
the doc lists no description for this module, so run it once and read the bundle before you map anything from it.
ReviewStudio2Watch New Clients

Watch New Clients

triggerIn the docs only

Picks up every client added to ReviewStudio and hands it to the next module as a bundle, one bundle per client, ready to copy into a CRM or to seed a project.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a client added right after a check waits for the next one.
When to use it
when onboarding a client should open a project or a folder somewhere else without a manual step.
Watch out
on the Free plan the shortest interval is 15 minutes, so plan around that delay.
ReviewStudio3Watch New Projects

Watch New Projects

triggerIn the docs only

Brings each project created in ReviewStudio into your scenario at the next check, which keeps planning tools, channels and trackers in step with what the studio actually launched.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the new projects since the previous run, each as its own bundle.
When to use it
when a new project should appear in your project management tool or trigger a kickoff message.
Watch out
every project found counts as an operation for each module after it, so keep the chain short.
ReviewStudio4Watch New Reviews

Watch New Reviews

triggerIn the docs only

Lets a newly opened review kick off work elsewhere, such as notifying the reviewers or logging the round in a spreadsheet the account manager reads.

How it fires
scheduled. Make checks the app on the scenario's schedule and brings back the reviews created since the last check.
When to use it
when each review round needs a trace outside ReviewStudio, for reporting or for billing by round.
Watch out
this trigger sees new reviews, not decisions on them; for sign-offs, pick Watch New Approval Decisions instead.
Modules

Every ReviewStudio module in Make

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

ReviewStudio1

Create a Client

ActionIn the docs only

Adds a client to ReviewStudio straight from another tool, so the name your sales team typed once is the name reviewers see.

When to use it
when a deal is won in your CRM and the client should exist in ReviewStudio before the first file arrives.
Watch out
run a List Clients search first if the same client could already be there.
ReviewStudio2

Create a Project

ActionIn the docs only

Opens a new project in ReviewStudio with data mapped from earlier modules, which saves the setup step at the start of every job.

When to use it
right after Watch New Clients, or when a signed quote in another app means work can begin.
Watch out
map data from a real bundle rather than typed text, and check the result with Run once before you schedule it.
ReviewStudio3

Create a Review

ActionIn the docs only

Starts a review round from your scenario instead of the ReviewStudio screen, so a delivery in one tool can open feedback in the other.

When to use it
when a new version of a creative is ready and the review should open without someone clicking through the app.
Watch out
map the right project; a review attached to the wrong one confuses the client.
ReviewStudio4

Delete a Client

ActionIn the docs only

Removes a client from ReviewStudio when it is gone from your source of truth, which keeps the client list short and honest.

When to use it
when an account is closed in your CRM and should disappear from the review tool as well.
Watch out
a delete cannot be undone from Make, so test it on a dummy client with Run once first.
ReviewStudio5

Delete a Project

ActionIn the docs only

Clears a project out of ReviewStudio from inside a scenario, handy for test projects or jobs cancelled before they started.

When to use it
when a cancelled order in another app should remove the matching project here.
Watch out
nothing brings it back afterward; add a filter so only the intended project reaches this module.
ReviewStudio6

Delete a Review

ActionIn the docs only

Takes a single review off the board, useful when a round was opened by mistake or duplicated by an earlier scenario.

When to use it
when cleaning up reviews created in error, one at a time, by their ID.
Watch out
Make cannot restore it once the module has run, so double check the ID you map.
ReviewStudio7

Get a Client

ActionIn the docs only

Fetches one client when you already have its ID, so later modules can use its details without asking you to type anything.

When to use it
when a trigger hands you a client ID and the next step needs the full record.
Watch out
this needs an exact ID; to find a client by browsing, List Clients is the module to pick.
ReviewStudio8

Get a Project

ActionIn the docs only

Reads a single project from ReviewStudio and makes its data available to every module that follows in the scenario.

When to use it
after Watch New Approval Decisions, when you want the project behind the decision before notifying anyone.
Watch out
it returns one record only; if you need several projects, List Projects gives you a bundle for each.
ReviewStudio9

Get a Review

ActionIn the docs only

Pulls one review by its ID, which gives a notification or a report the exact round it is talking about.

When to use it
when a message to a client should quote the review a decision refers to.
Watch out
the bundle it returns has no documented field list, so run it once and read the output before mapping it.
ReviewStudio10

List Clients

SearchIn the docs only

Returns your ReviewStudio clients as separate bundles, a good base for a sync, an audit or a check before you create anything.

When to use it
when you need to know whether a client already exists, or to copy the whole list into a sheet.
Watch out
a search can return zero, one or many bundles, and each one runs the next modules once.
ReviewStudio11

List Projects

SearchIn the docs only

Brings back projects one bundle at a time, so you can loop over them to report, archive or match them against another tool.

When to use it
when building a status report of open work, or reconciling projects with your invoicing app.
Watch out
many results means many operations downstream; filter early to spend fewer of them.
ReviewStudio12

List Reviews

SearchIn the docs only

Collects existing reviews as individual bundles, which turns scattered rounds into a list you can log, count or send.

When to use it
when an account manager wants every review in one place, or before deciding which round to update.
Watch out
an empty result is valid, so the modules after it simply do not run; plan for that case.
ReviewStudio13

Make an API Call

ActionIn the docs only

Calls any endpoint of the ReviewStudio API with the connection you already have, covering whatever the listed modules leave out.

When to use it
when a job you need exists in the ReviewStudio API but has no ready module in Make.
Watch out
you write the request yourself, so keep the ReviewStudio API documentation open next to the editor.
ReviewStudio14

Update a Client

ActionIn the docs only

Changes an existing client in ReviewStudio so its details follow what your CRM or billing tool says, without editing it by hand.

When to use it
when a client renames itself or changes contact in another app and ReviewStudio should follow.
Watch out
you need the client ID; get it from a trigger or from List Clients before this step.
ReviewStudio15

Update a Project

ActionIn the docs only

Edits a project already in ReviewStudio, which lets an event elsewhere move a job forward without anyone opening the app.

When to use it
after Watch New Approval Decisions, to reflect a sign-off on the project it concerns.
Watch out
only map the fields you mean to change, and test with Run once on a single project.
ReviewStudio16

Update a Review

ActionIn the docs only

Adjusts a review that already exists, so the round stays accurate when a deadline or detail changes in another tool.

When to use it
when the planning tool moves a delivery and the open review should reflect it.
Watch out
pick the review by ID with Get a Review or List Reviews first; guessing the round is how wrong files get edited.
Need help

Need help automating ReviewStudio with Make?

A person reads every message.

FAQ

ReviewStudio and Make: common questions

01Is the ReviewStudio Make integration free?
Yes, on the Make side. ReviewStudio 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 and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits, meaning operations, each month. You still need your own active ReviewStudio account, which ReviewStudio bills separately on its pricing page.
02What do you need to connect ReviewStudio to Make?
An active ReviewStudio account and its API key. In ReviewStudio, open Settings from the main menu, go to the Configuration tab and copy the value in the API key field. Then in Make, add any ReviewStudio module, click Create a connection, give it an optional name and paste the key. That one connection is reused by all 20 ReviewStudio modules, so you only do this once per account. If a module later reports an authentication error, check that the key in the connection still matches the one in ReviewStudio.
03Do ReviewStudio triggers in Make fire instantly?
Most likely not. Make's doc does not state their type, but all 4 are Watch triggers with no instant tag listed, so they work as scheduled triggers: Make checks ReviewStudio on the scenario's schedule instead of being called the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest gap, while paid plans go down to 1 minute. For approvals, clients, projects and reviews that rarely need a reaction within seconds, this is usually enough. Anything created between two checks is picked up at the next one.
04What if a ReviewStudio module you need is missing in Make?
Use Make an API Call. It is part of the 20 modules and calls any endpoint of the ReviewStudio API with the same connection, so you can reach what the 13 actions and 3 searches do not cover. You write the request yourself, which means reading the ReviewStudio API documentation. Also note that Make's documentation for this app is flagged as AI-generated from the vendor's docs, so check important details with ReviewStudio directly.
05Should you use Make or n8n with ReviewStudio?
It depends on the tool your team already knows. The same app often has an n8n node too, so the choice rarely comes down to ReviewStudio itself. On the Make side, you get 20 ready modules, a connection built once and the scenario editor with Run once for testing. Compare both editors on your own scenario, the one you actually need, before committing. The comparison page linked above lists the criteria without ranking either tool.
Same platform

Other docs you might need on this stack.

Browse all integrations