Resources · Make integration

AddMe Reviews Make integrationAutomate AddMe Reviews with Make.

What if every happy customer got a review request without anyone typing it? The AddMe Reviews Make integration gives you 8 action modules to add customers and send email or SMS review requests. This page walks a first-time Make user through the connection and a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the AddMe Reviews Make integration do for you?

The AddMe Reviews Make integration links your AddMe Reviews account to Make so that a scenario, the automation you build in Make, can add customers and ask them for a review on its own. Each step of that scenario is a module, and AddMe Reviews brings 8 of them, all actions: nothing in the app starts a scenario by itself.

Ask for a review right after a sale. When another app records a finished job or a paid order, Create an Email Review Request or Create a SMS Request sends the ask while the experience is still fresh. Pick the channel your customers actually read.

Keep one clean customer list. Get a Customer By Email looks up the person first; depending on the result, Update a Customer refreshes the record or Create a Customer adds it. You avoid duplicates before any message goes out.

Send the request later, not now. Create a Scheduled Email Request and Create a Scheduled SMS Request exist for requests that should leave at a later moment, for example once the service has been delivered.

Know the limits before you start: Make's own documentation for this app is marked as limited, because little public information about AddMe Reviews exists. When a listed module falls short, Make an API Call reaches the rest of the AddMe Reviews API with the same connection. The app may also have an n8n node; the n8n vs Make comparison helps you choose. New to the editor? The Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect AddMe Reviews to Make?

  1. 01

    Add an AddMe Reviews module

    In your scenario, add any AddMe Reviews module and click Create a connection. A connection is your AddMe Reviews account linked to Make once, then reused by all 8 modules.

  2. 02

    Name the connection

    Giving it a name is optional, but a clear one such as the name of the shop or the client account saves confusion later, especially if you manage reviews for more than one business.

  3. 03

    Authorize Make and save

    Either approve Make on the AddMe Reviews page that opens, or paste the key AddMe Reviews gives you, depending on what the window asks for. Then click Save and the module is ready to fill.

First scenario

Your first scenario: a review request after every sale

GoalWhen another app hands over a customer's email, Make checks AddMe Reviews for that customer and sends an email review request.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Since AddMe Reviews has no trigger, start with the app that knows about your customers, such as a form or a shop.

  2. 02

    Look up the customer

    Click the + on the right to add Get a Customer By Email, pick your connection, and map the email coming from the first module. Make passes data from one module to the next as bundles, one customer per bundle. Test once with an email that is not on file yet: if nothing comes back, add Create a Customer before the request.

  3. 03

    Send the review request

    Add Create an Email Review Request with the next +, and fill its fields with the data mapped from the previous modules.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Open each module's bubble to read the bundles it received, and check in AddMe Reviews that the request really went out.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Every module execution counts as an operation on your Make plan.

Modules

What the AddMe Reviews modules do

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

AddMe Reviews1

Create a Customer

ActionIn the docs only

Adds a new customer to AddMe Reviews from data sent by another app, so the person exists there before you ask them for anything.

When to use it
right after Get a Customer By Email found nobody, to register a buyer or client the first time they appear.
Watch out
running it without that lookup first can create the same person twice.
AddMe Reviews2

Create a SMS Request

ActionIn the docs only

Sends a review request by text message, which suits customers who rarely open their email but always read their phone.

When to use it
for businesses where the customer leaves with a phone number rather than an email, like a salon or a repair shop.
Watch out
a text reaches the person immediately, so test with your own number first.
AddMe Reviews3

Create a Scheduled Email Request

ActionIn the docs only

Prepares an email review request meant to go out at a later moment instead of right away, as the module name says.

When to use it
when asking too early would feel pushy, for instance when the product still has to reach the customer.
Watch out
the documentation does not describe how the send time is set, so check the fields Make shows once your connection exists.
AddMe Reviews4

Create a Scheduled SMS Request

ActionIn the docs only

The text message version of the delayed request: the SMS is lined up now and meant to leave later.

When to use it
for appointment businesses that want the ask to arrive after the visit rather than while the customer is still at the counter.
Watch out
test it on your own number with Run once, since the documentation gives no detail on timing.
AddMe Reviews5

Create an Email Review Request

ActionIn the docs only

Emails a customer an invitation to leave a review, the most direct way to turn a finished sale into feedback.

When to use it
as the last module of a scenario that starts when an order is paid or a job is marked done in another app.
Watch out
the request leaves as soon as the module runs, so map the right email before switching on.
AddMe Reviews6

Get a Customer By Email

ActionIn the docs only

Finds an existing AddMe Reviews customer from an email address and hands the record to the next modules of the scenario.

When to use it
before any create or update step, so the scenario knows whether the person is already on file.
Watch out
test it with Run once on an email that is not on file, to see what the next module receives when nobody matches.
AddMe Reviews7

Make an API Call

ActionIn the docs only

Calls any endpoint of the AddMe Reviews API with the connection you already set up, for everything the seven other modules do not cover.

When to use it
when a listed module stops short, say a piece of data or an action it does not offer.
Watch out
you need the AddMe Reviews API reference to know which endpoint to call, and Make's documentation for this app stays limited.
AddMe Reviews8

Update a Customer

ActionIn the docs only

Changes the details of a customer who is already in AddMe Reviews, so your review requests go to the right address or number.

When to use it
when your CRM or shop records a new phone number or email for someone AddMe Reviews already knows.
Watch out
place Get a Customer By Email before it to target the right record.
Need help

Need help automating AddMe Reviews with Make?

A person reads every message.

FAQ

Common questions about AddMe Reviews and Make

01Is the AddMe Reviews Make integration free?
Yes, AddMe Reviews is a standard app in Make, so you can use it on the Free plan. That plan keeps you to 2 active scenarios, a minimum of 15 minutes between two 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) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module execution. Your AddMe Reviews subscription is a separate matter that Make does not handle.
02What do you need to connect AddMe Reviews to Make?
An AddMe Reviews account and a Make account. Make's documentation lists no special prerequisite for this app and gives no dedicated connection steps, so the generic flow applies: add an AddMe Reviews module, click Create a connection, optionally name it, then approve Make on the AddMe Reviews page or paste the key the app provides, and click Save. The same connection then works for all 8 modules, including Make an API Call, so you only do it once per account.
03Can AddMe Reviews start a Make scenario in real time?
No, AddMe Reviews has no trigger module in Make, scheduled or instant, so it cannot start a scenario by itself. You still have two ways in. Start the scenario with a trigger from another app, such as the shop, form or booking tool where customers appear, and let it feed the AddMe Reviews modules. Or put a schedule on the first module so Make runs the scenario at a set interval, every 15 minutes by default. For real-time behavior, the trigger of that other app has to be an instant one.
04What if an AddMe Reviews module is missing in Make?
First check what the 8 modules already do. They cover customers (create, update, find by email) and review requests by email or SMS, sent now or later. For anything else, the Make an API Call module lets you call any endpoint of the AddMe Reviews API with the connection you already have. Be aware that Make marks its documentation for this app as limited, since little public information about AddMe Reviews exists, so you will need the app's own API reference to build that call correctly.
05Should you use Make or n8n for AddMe Reviews?
It depends on the tool your team already works in. In Make, AddMe Reviews offers 8 action modules, Make an API Call included, and it runs on every plan, Free included. The same app may also exist as an n8n node, so check there if n8n is your daily tool. The useful test is practical: can the other apps in your review flow, the shop or the booking tool, be reached from the same platform? Choose the one where the whole chain fits, rather than splitting the flow across two tools.