Resources · Make integration

CleverReach Make integrationAutomate CleverReach with Make.

Your newsletter list can keep itself up to date. The CleverReach Make integration gives you 16 modules: 4 scheduled triggers, 10 actions and 2 searches. This guide shows marketers how to link the account, build a first scenario and pick the right module.

Try the CleverReach integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the CleverReach Make integration do?

The CleverReach Make integration links your CleverReach account to Make so that subscribers and order items move between your newsletter tool and your other apps without copy and paste. You build a scenario, which is the automation itself, out of modules, the bricks that each watch, create, read or change one thing in CleverReach.

A list fed straight from your shop. When a buyer checks out in your store app, Create a Subscriber adds the address to CleverReach and Create an Order Item records the purchase, so your next campaign can speak to recent buyers.

Unsubscribes that reach your CRM. Watch Unsubscribers spots contacts who left the list, and the next module updates their record in your sales tool so nobody writes to them by hand.

A heads-up when a campaign is drafted. Watch Campaigns notices each new mailing, and Make can pass its details to the chat tool your team already reads.

All four triggers are scheduled: Make checks CleverReach on the scenario's schedule, so nothing arrives the second it happens. For any call the listed modules leave out, Make an API Call reaches the CleverReach API with the same connection. The CleverReach documentation in Make is marked as AI-generated, so check important details with CleverReach directly.

Comparing tools first? Read our n8n vs Make comparison, see the plans in Make pricing, or learn the editor with Make training.

Connect

How do you connect CleverReach to Make?

  1. 01

    Create an OAuth app in CleverReach

    In CleverReach, open Account, then Interfaces and REST API, and create a new OAuth app. Enter https://www.integromat.com/oauth/cb/cleverreach as the callback URI, then copy the Client ID and the Client secret shown on screen.

  2. 02

    Add a CleverReach module in Make

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

  3. 03

    Paste the credentials and confirm

    Paste the Client ID and Client secret you copied, or follow the instructions Make shows on screen. Once the connection is saved, the module can read your CleverReach account and you can fill its fields.

First scenario

Build your first CleverReach scenario

GoalWhen someone signs up in another app, Make adds that person to CleverReach as a subscriber.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Pick the app where sign-ups happen, such as your form or shop tool, as the first module.

  2. 02

    Add Create a Subscriber

    Click the + on the right of that first module, search for CleverReach and choose Create a Subscriber. Select your connection, or click Create a connection if it is your first CleverReach module.

  3. 03

    Map the contact data

    Fill the module fields by mapping values from the first module, such as the email address it received. Each contact travels as a bundle, one item passed from a module to the next.

  4. 04

    Test with Run once

    Click Run once, then trigger a test sign-up. Open the bubbles above each module to read the bundles they received and confirm the new subscriber appears in CleverReach.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on. Each module run counts as one operation on your Make plan.

Triggers

What starts a CleverReach scenario?

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

CleverReach1Watch Campaigns

Watch Campaigns

Scheduled trigger

In Make“Triggers when a new mail campaign is created.”

Watch Campaigns tells your team about every new mail campaign created in CleverReach, so a draft never goes out unseen. Each new campaign becomes one bundle that the next module can post, log or forward.

How it fires
scheduled. Make checks CleverReach on the scenario's schedule, every 15 minutes by default, and picks up the campaigns created since the last check.
When to use it
when several people prepare mailings and a reviewer wants a note in the team chat at the next run after a new one is created.
CleverReach2Watch Order Items

Watch Order Items

Scheduled trigger

In Make“Triggers when a new order item is created.”

Watch Order Items hands you each new order item recorded in CleverReach, ready to copy into a spreadsheet, a reporting tool or an email to whoever handles fulfillment.

How it fires
scheduled. Make polls CleverReach at the interval set on the first module, so new items arrive in batches rather than one by one the moment they appear.
When to use it
when order data already lands in CleverReach and another team needs the same items without logging in.
CleverReach3Watch Subscribers

Watch Subscribers

Scheduled trigger

In Make“Triggers when a new subscriber is created.”

Watch Subscribers gives you every new contact added to CleverReach, so your CRM or welcome process learns about sign-ups without an export. Each subscriber flows on as its own bundle.

How it fires
scheduled. Make asks CleverReach for new subscribers on the scenario's schedule; on the Free plan the shortest gap between two runs is 15 minutes.
When to use it
when people join your list through CleverReach forms and your sales tool should hold the same contacts.
Watch out
it reacts to new subscribers only; a changed address on an existing contact does not start the scenario.
CleverReach4Watch Unsubscribers

Watch Unsubscribers

Scheduled trigger

In Make“Triggers when a new unsubscriber is appeared.”

Watch Unsubscribers surfaces the contacts who have left your CleverReach list, so every other tool can respect that choice too. Each departure becomes a bundle you can pass to an update module in another app.

How it fires
scheduled. Make checks CleverReach for new unsubscribers each time the scenario runs, on the schedule you set.
When to use it
when the same people also receive messages from a CRM or a support tool, and you want those tools updated at the next run.
Modules

What can Make do in CleverReach?

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

CleverReach1

Create an Order Item

Action

In Make“Creates a new order item.”

Create an Order Item writes a purchase into CleverReach from another app, so your newsletter tool knows what a contact bought and your segments can build on it.

When to use it
right after a checkout module in your store app, when the sale lives outside CleverReach.
Watch out
run it once per sale; a replayed scenario creates a second item.
CleverReach2

Create a Subscriber

Action

In Make“Creates a new subscriber.”

Create a Subscriber adds a new contact to CleverReach, which saves you from importing files each time a form or a shop collects addresses.

When to use it
behind a sign-up form, a webinar registration or a checkout in another app.
Watch out
if the person may already be on your list, search first with Get a Subscriber and update instead.
CleverReach3

Deactivate a Subscriber

Action

In Make“Sets subscriber status to not active.”

Deactivate a Subscriber sets a contact to not active, so mailings stop reaching that person while the record stays in CleverReach.

When to use it
when someone opts out in another tool, a CRM or a support desk, and CleverReach has to follow.
Watch out
it pauses the contact; pick Delete a Subscriber only when the record itself must go.
CleverReach4

Delete an Order Item

Action

In Make“Deletes a specific order item.”

Delete an Order Item removes one purchase record from CleverReach, which keeps your buyer segments honest when a sale is cancelled elsewhere.

When to use it
after a refund or a cancellation step in your shop or billing app.
Watch out
a deletion cannot be undone from the scenario, so test with Run once on a dummy item before switching the scenario on.
CleverReach5

Delete a Subscriber

Action

In Make“Deletes a specific subscriber.”

Delete a Subscriber erases a contact from CleverReach entirely, the right move when a person asks for their data to be removed.

When to use it
at the end of an erasure request handled in another tool, once the other systems are cleaned too.
Watch out
treat it as final; for a simple opt-out, Deactivate a Subscriber is the safer choice.
CleverReach6

Get an Order Item

Action

In Make“Gets a single order item.”

Get an Order Item fetches one purchase you already know, giving the next modules its full details instead of the few values a trigger passed along.

When to use it
before an update or a report, when you hold the item's identifier from an earlier module.
Watch out
it reads a single item; to scan many, List Order Items is the module to pick.
CleverReach7

Get a Subscriber

Action

In Make“Gets a single subscriber.”

Get a Subscriber pulls up one contact from CleverReach, so a scenario can check who someone is before it creates, changes or deactivates anything.

When to use it
as a lookup step between a trigger from another app and an update in CleverReach.
Watch out
plan a filter or a router for the case where the contact is not found, so the next module does not fail.
CleverReach8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the CleverReach API from your scenario, with the connection you already set up, when no listed module does the job.

When to use it
for a CleverReach feature that none of the other 15 modules covers.
Watch out
you write the request yourself, so keep the CleverReach API reference open while you build it.
CleverReach9

Update an Order Item

Action

In Make“Updates a specific order item.”

Update an Order Item corrects a purchase already stored in CleverReach, so a changed order in your shop does not leave stale data behind in your newsletter tool.

When to use it
when an order is edited in the store app and CleverReach should show the new version.
Watch out
you need the item's identifier; fetch it with List Order Items or Get an Order Item first.
CleverReach10

Update a Subscriber

Action

In Make“Updates a specific subscriber.”

Update a Subscriber changes the details of an existing contact, which keeps CleverReach in line with the CRM where your team actually edits people.

When to use it
after a contact record changes in your sales or support tool.
Watch out
test with Run once on one contact and check the result in CleverReach before switching the scenario on.
CleverReach11

List Order Items

Search

In Make“Lists all order items.”

List Order Items returns the purchases stored in CleverReach as separate bundles, so you can copy them to a sheet or check them one by one.

When to use it
for a first sync of existing orders into another tool, before Watch Order Items takes over the new ones.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle.
CleverReach12

List Subscribers

Search

In Make“Lists all subscribers for specific group.”

List Subscribers gives you the contacts of a specific CleverReach group, one bundle per person, ready to sync into another tool or audit.

When to use it
to copy an existing group into your CRM before Watch Subscribers handles the new sign-ups.
Watch out
a large group means many bundles, and each module that follows spends one operation per contact.
Need help

Need help automating CleverReach with Make?

A person reads every message.

FAQ

CleverReach and Make: common questions

01Is the CleverReach Make integration free?
Yes, CleverReach is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the limit on active scenarios. Your CleverReach subscription is separate and is billed by CleverReach, not by Make.
02What do you need to connect CleverReach to Make?
You need an active CleverReach account and an OAuth app created inside it. In CleverReach, go to Account, then Interfaces and REST API, create the OAuth app, enter the Make callback URI and copy the Client ID and Client secret. In Make, add a CleverReach module, click Create a connection and paste both values. The same connection then serves all 16 CleverReach modules in every scenario you build, so you only do this setup once.
03Do CleverReach triggers in Make fire in real time?
No. All 4 CleverReach triggers are scheduled: Make asks CleverReach for new campaigns, order items, subscribers or unsubscribers each time the scenario runs. A new scenario runs every 15 minutes by default. On a paid plan you can shorten the interval to 1 minute, while the Free plan keeps a minimum of 15 minutes. If you need a reaction closer to the event, start the scenario from the other app instead.
04What if a CleverReach action is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the CleverReach API with the connection you already created, so a feature without its own module is still reachable. You write the request yourself, using the CleverReach API reference. Keep in mind that the CleverReach documentation in Make is labelled as AI-generated, so confirm important details with CleverReach before you rely on them in a live scenario.
05Should you use Make or n8n for CleverReach?
It depends on the tool your team already uses. In Make, CleverReach comes with 16 ready modules covering subscribers, order items and campaigns, a guided connection and a Free plan to test on. n8n is another automation tool, and many apps have a node there too, so check what it offers for CleverReach before deciding. Compare the modules you actually need, the way each tool counts usage and how comfortable your team feels in each editor.
Same platform

Other docs you might need on this stack.

Browse all integrations