Resources · Make integration

Clepher Make integrationAutomate Clepher with Make.

Can Make react to your Clepher subscribers without a single line of code? Yes. The Clepher Make integration gives you 2 instant triggers and 9 modules to tag people, send cards or flows and update custom fields. This page walks you from connection to a first working scenario.

Try the Clepher integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Clepher Make integration let you automate?

The Clepher Make integration links your Clepher account to Make, a visual tool where you chain apps into a scenario, meaning the automation you build. Clepher can alert Make the moment someone subscribes to your page or gets a tag, and Make can answer back by tagging, messaging or updating that subscriber.

A welcome path that starts by itself. Put Watch New Subscribers first, then Send Flow, and every new subscriber lands in the sequence you designed in Clepher, without anyone clicking a button. Add Attach Tag right after if you want to mark who already received it.

Segments that follow what happens elsewhere. Another app in your stack can open the scenario, for example a form tool (see the 123FormBuilder Make integration). Find User by Evidence looks up the matching subscriber from what the form collected, then Set Custom Field or Detach Tag keeps Clepher in line with the answers.

A tag that acts as a switch. Watch New Tagged Subscribers fires when a tag is attached, so a support rep or a sales rep can tag a lead in Clepher and let Make send the right card.

Know the limits before you start: Make flags its Clepher documentation as limited. It names the 11 modules but says little about their fields. Make an API Call covers what the listed modules miss. If you are still choosing your tool, read n8n vs Make, and when a scenario misbehaves, Make troubleshooting lists the usual fixes.

Connect

How do you connect Clepher to Make?

  1. 01

    Add a Clepher module

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

  2. 02

    Give the connection a name

    This step is optional, but a clear name such as the page it belongs to helps when you run several Clepher accounts. You will spot the right one in the dropdown without guessing.

  3. 03

    Authorize and save

    Approve Make on the Clepher authorization page, or paste the key Clepher gives you if Make asks for one. Then click Save, and the module can read your Clepher data.

First scenario

Your first scenario: send a flow when a tag is attached

GoalWhen a tag is attached to a subscriber in Clepher, Make sends that subscriber a flow.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place your first module, the brick that starts everything.

  2. 02

    Pick Watch New Tagged Subscribers

    Search for Clepher, choose Watch New Tagged Subscribers and create or select your connection. Fill in the fields the module shows, using the lists Make reads from your account.

  3. 03

    Add Send Flow

    Click the + on the right of the trigger and add Send Flow. Map the subscriber coming from the trigger, then choose the flow that person should receive.

  4. 04

    Test with Run once

    Click Run once and attach a tag to a test subscriber in Clepher. Open each module to read the bundles it received, a bundle being one item passed along, here one subscriber.

  5. 05

    Switch it on

    Check the clock on the first module, then switch the scenario on. From now on, each tagged subscriber gets the flow, and each module run counts as one operation on your plan.

Triggers

What can start a Clepher scenario?

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

Clepher1Watch New Subscribers

Watch New Subscribers

Instant trigger

In Make“Triggers when a new user subscribes to your page.”

You get a scenario that starts on its own each time someone new subscribes to your page, with that subscriber handed over as a bundle to the next modules. It is the natural door for any welcome logic.

How it fires
instant, Clepher calls Make through a webhook as soon as it happens, the lightning badge on the module.
When to use it
pick it when the moment of subscribing is what matters, for a welcome flow or a first tag.
Watch out
every new subscriber runs the whole scenario, so each module in the chain spends operations on every signup.
Clepher2Watch New Tagged Subscribers

Watch New Tagged Subscribers

Instant trigger

In Make“Triggers when a new tag is attached to a subscriber.”

This one hands your team a remote control: attach a tag in Clepher and Make picks up that subscriber right away to do the next step. Tags become commands, not just labels.

How it fires
instant, Clepher calls Make through a webhook as soon as it happens, no polling interval involved.
When to use it
choose it over Watch New Subscribers when a person or a Clepher flow decides who moves forward, such as a lead marked as qualified.
Watch out
if the same scenario later runs Attach Tag on that subscriber, you may start it again, so tag with care.
Modules

What can Make do in Clepher?

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

Clepher1

Attach Tag

Action

In Make“Attach a tag to a subscriber.”

Your subscriber leaves the scenario with a tag on their profile, so Clepher and your team can sort them by what just happened, such as a purchase or a form reply.

When to use it
at the end of a chain, to record that a subscriber has been handled.
Watch out
a tag added here can start a scenario that uses Watch New Tagged Subscribers.
Clepher2

Detach Tag

Action

In Make“Detach a tag from a subscriber.”

A subscriber loses a tag that no longer fits, which keeps your segments honest when a situation changes, for instance a trial that turned into a paid account.

When to use it
right after an event in another app proves the old label is outdated.
Watch out
removing a tag does not undo what that tag already triggered in Clepher.
Clepher3

Find User by ID

Action

In Make“Finds a subscriber by profile ID”

Hand it a profile ID and it brings back the matching subscriber, ready for the next modules to read or update. It is the quickest route when you already stored that ID somewhere.

When to use it
when a spreadsheet or a CRM row keeps the Clepher profile ID next to the contact.
Watch out
Make lists it as an action, even though it only looks a subscriber up.
Clepher4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With the same connection, this module reaches any endpoint of the Clepher API, which covers every request the other modules do not offer. You write the request yourself. Comfortable reading an API reference? Then it is for you.

When to use it
only after checking that none of the listed modules does the job.
Watch out
Make publishes limited documentation for Clepher, so keep the Clepher API reference open while you build the request and test it with Run once.
Clepher5

Send Card

Action

In Make“Send a card to a subscriber.”

One message goes out to one subscriber: a single card, without starting a whole sequence. That keeps the reply short when all you need is a confirmation or a single offer.

When to use it
for a one-off notice tied to an event, such as an order that shipped.
Watch out
when the conversation needs several steps, Send Flow is the better fit.
Clepher6

Send Flow

Action

In Make“Send a flow to a subscriber.”

The subscriber enters a full flow you already built in Clepher, with its own steps and branches, so Make only has to choose who and when. The conversation design stays in Clepher.

When to use it
for onboarding, a nurturing sequence or a qualification path started from outside Clepher.
Watch out
build and test the flow in Clepher first, Make simply points to it.
Clepher7

Set Custom Field

Action

In Make“Set a custom field for a subscriber.”

A value from another app lands in a custom field of the subscriber, so your Clepher messages can reuse it later, such as a plan name or an order status.

When to use it
when data lives in a form, a store or a CRM and your flows need it.
Watch out
Make documents no format for Clepher fields, so check the stored value with Run once before going live.
Clepher8

Unset Custom Field

Action

In Make“Unset a custom field for a subscriber.”

This clears a custom field on a subscriber, which stops a stale value, like an expired discount code, from showing up in the next message you send.

When to use it
once the information behind the field is no longer true.
Watch out
the value is gone from Clepher afterwards, so copy it elsewhere first if you still need it.
Clepher9

Find User by Evidence

Search

In Make“Finds a subscriber by evidence.”

You get the subscribers matching the evidence you give Clepher, a way to find someone when the profile ID is not at hand. As a search module, it can return zero, one or several bundles.

When to use it
before Attach Tag or Send Card, when you only know details from another app.
Watch out
plan for zero results, or the modules after it simply get nothing to work on.
Need help

Need help automating Clepher with Make?

A person reads every message.

FAQ

Questions people ask next

01Is the Clepher Make integration free?
Yes, Clepher is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes, handles files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow runs of 40 minutes. Usage is counted in operations, one module processing one bundle. Your Clepher subscription is a separate matter and is not covered here.
02What do you need to connect Clepher to Make?
A Clepher account and a Make account are enough to begin. Make's documentation lists no specific prerequisite and no dedicated connection steps for Clepher, so you follow the standard path: add a Clepher module, click Create a connection, name it if you wish, approve Make on the Clepher side or paste the key Clepher gives you, then click Save. The connection is stored once and every Clepher module in your scenarios can reuse it, including Make an API Call.
03Do Clepher triggers fire in real time?
Yes. Both Clepher triggers are instant: Watch New Subscribers and Watch New Tagged Subscribers rely on Clepher calling Make through a webhook as soon as the event happens. You will see the lightning badge on the module instead of the clock badge used by scheduled triggers. The Free plan interval of 15 minutes applies to scheduled scenarios, not to these two. Remember that every event starts a run, and each module in the chain uses an operation.
04What if a Clepher module you need is missing in Make?
It depends on the request. The 11 modules cover subscribers, tags, cards, flows and custom fields. For anything else, Make an API Call reaches any endpoint of the Clepher API with the connection you already have. Make flags its Clepher documentation as limited, so field details are thin on its side and you will lean on Clepher's own API reference. Test every new call with Run once and read the bundle it returns before switching the scenario on.
05Should you use Make or n8n for Clepher?
It depends on the criteria that matter to you. On Make, Clepher offers 11 ready modules, 2 instant triggers and Make an API Call for the rest, and it runs on the Free plan. Many apps also exist as an n8n node, so check whether one exists for Clepher and compare the modules each tool lists against the steps your scenario needs. Pick the tool whose modules cover your case with the fewest custom requests, and the one your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations