Resources · Make integration

Judge.me Make integrationAutomate Judge.me with Make.

Every new product review can start work for you the moment it lands. The Judge.me Make integration gives you 2 modules: an instant trigger for new reviews and an API call for the rest. This guide shows store owners how to connect the account and run a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Judge.me Make integration do for your store?

The integration links your Judge.me account to Make, a no-code automation tool. You build a scenario, which is the automation itself: a chain of modules, each module being one brick such as a trigger or an action. Judge.me brings two of those bricks, so a fresh review can flow straight into the other tools your shop already uses.

Put each new review in front of the right person. Watch Reviews reacts as soon as a customer posts, and the next module can drop that review into a chat channel, a spreadsheet or your help desk. Support sees an unhappy buyer while the order is still fresh in everyone's mind.

Keep a running log of feedback. Every review arrives as a bundle, the single item Make passes from one module to the next. Map it into a sheet or a database and the product team gets one place to read what shoppers say, with no copy and paste.

Reach what the listed modules skip. Make an API Call sends a request to the Judge.me API with the connection you already set up, which covers any endpoint the two named modules do not.

Keep the scope in mind: this app has one trigger and one generic action, nothing more. Everything past new reviews goes through the API call, so a quick look at the Judge.me API reference helps. If you are still weighing platforms, the n8n vs Make comparison lays out the differences, and the Make review covers the tool as a whole. Teams that want help building the flow can talk to our Make agency.

Connect

How do you connect Judge.me to Make?

  1. 01

    Copy your Judge.me API key

    You need an active Judge.me account. From your shop's Apps page, open Judge.me, then go to Settings, Integrations, Developers and Judge.me API. Copy the API key shown there, and note your shop domain too.

  2. 02

    Add the Judge.me module

    In Make, add a Judge.me module to your scenario and click Create a connection. A connection is your Judge.me account linked to Make once, then reused by every Judge.me module. The Connection name field is optional.

  3. 03

    Paste your credentials

    Enter the shop domain and API token you copied, or follow the on-screen instructions Make displays. Save, and the connection shows up in the module, ready for the next Judge.me brick you add.

First scenario

Build your first scenario: act on each new review through the API

GoalWhen a customer posts a review in Judge.me, Make calls the Judge.me API endpoint you choose for that review.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. This empty canvas is where the automation takes shape.

  2. 02

    Add Watch Reviews

    Search for Judge.me, pick Watch Reviews, click Create a webhook, then Create a connection with your shop domain and API token.

  3. 03

    Add Make an API Call

    Click the + on the right of the trigger and pick Make an API Call from Judge.me. It reuses your connection. Choose the endpoint in the Judge.me API reference and map the review data into the request.

  4. 04

    Test with Run once

    Click Run once, then post or wait for a real review. Open each module's bubble to read the bundle it received and check the data lands where you expect.

  5. 05

    Switch it on

    Turn the scenario on. Since the trigger is instant, Judge.me calls Make as soon as a review comes in, so no polling interval needs tuning here.

Triggers

What starts a Judge.me scenario

1 module starts a scenario when something happens in Judge.me. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Judge.me as soon as it happens.

Judge.me1Watch Reviews

Watch Reviews

Instant trigger

In MakeWatches for new reviews.

Hands your scenario each new review left on your store, so feedback reaches the people who can act on it without anyone refreshing the Judge.me dashboard. Each review arrives as its own bundle for the next module to use.

How it fires
instant. Judge.me calls Make through a webhook as soon as the review is posted.
When to use it
you want support or the product team to read fresh reviews inside a tool they already open.
Watch out
it only watches new reviews, and it needs a webhook created before the connection when you set it up.
Modules

What else Make can do with Judge.me

Judge.me gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Judge.me1

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Gives you access to the whole Judge.me API from inside a scenario, reusing the connection you already created, so you are not limited to new reviews.

When to use it
the task you need is not covered by Watch Reviews, and the Judge.me API reference lists an endpoint for it.
Watch out
you write the request yourself, so check the endpoint and method in the vendor's documentation before running it.
Need help

Need help automating Judge.me with Make?

A person reads every message.

FAQ

Judge.me and Make: common questions

01Is the Judge.me Make integration free?
Yes, on the Make side. Judge.me 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, Enterprise) lift the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations, one run of one module on one bundle. Your Judge.me subscription is separate, so check its own pricing page.
02What does it take to connect Judge.me to Make?
An active Judge.me account and its API credentials: your shop domain and API token. You find the key in Judge.me under Settings, then Integrations, Developers and Judge.me API. In Make, add a Judge.me module, click Create a connection, name it if you like and paste the credentials. For the Watch Reviews trigger, Make first asks you to create a webhook, then the connection. After that, every Judge.me module in your scenarios reuses the same connection, so you only enter the key once.
03Does the Judge.me trigger in Make fire in real time?
Yes. Watch Reviews is an instant trigger: Judge.me calls Make through a webhook as soon as a new review is posted, and the scenario starts on that event. You will see a lightning badge on the module in the editor, which marks instant triggers. That differs from scheduled triggers, which Make checks on the scenario's schedule, every 15 minutes by default. Keep in mind the trigger only covers new reviews, so any other event has to be reached another way.
04What if a Judge.me module is missing in Make?
Use Make an API Call. It sends an authorized request to any endpoint of the Judge.me API with the connection you already set up, so the task does not have to exist as a named module. You pick the endpoint from the Judge.me API reference and build the request yourself. The Make documentation for this app is marked as AI-generated from the vendor's docs and may contain mistakes, so verify important details with Judge.me directly.
05Is Make or n8n better for Judge.me?
It depends on the tool your team already runs. On Make, Judge.me offers one instant trigger for new reviews plus Make an API Call for everything else, and it is available on the Free plan. The same app often has an n8n node as well. Check which operations each side lists for your case, and pick the platform where the rest of your workflows already live. Both can reach the Judge.me API when a named module is missing, so the choice rests on your stack rather than on this app.