Resources · Make integration

CloneByMe Make integrationAutomate CloneByMe with Make.

Can your CloneByMe agent answer and learn from inside your other tools? The CloneByMe Make integration gives you 5 modules: 1 trigger and 4 actions. This guide links your account, walks you through a first scenario and explains every module in plain words.

Try the CloneByMe integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the CloneByMe Make integration do for you?

The CloneByMe Make integration links your CloneByMe account to Make, a visual tool where you build a scenario: a chain of modules that runs on a schedule or when an app calls Make. Each module is one brick of that chain. Here you get one trigger, Watch Events, and four actions, including Get Agent Response and Train Agent.

Answers without opening the app. A question arrives in your form tool or your help desk. Get Agent Response asks your CloneByMe agent for a reply, and Send Response delivers it. Nobody copies and pastes between tabs.

An agent that keeps learning. When a new piece of content shows up elsewhere, Train Agent can pass it to CloneByMe, so the agent is not stuck with what you uploaded on day one.

CloneByMe activity in the rest of your stack. Watch Events picks up what happens in CloneByMe and hands it to the next module: a CRM, a sheet, a team chat.

Be aware of one real limit. The Make documentation for CloneByMe is marked as limited, and none of the 5 modules has an official description. Everything this page says about what a module does is read from its name, and the first Run once test is where you confirm it. If a module fails, the Make troubleshooting guide covers the usual errors.

The same app often has an n8n node too; the n8n vs Make comparison helps you pick a tool, and the Make review gives the broader picture.

Connect

How do you connect CloneByMe to Make?

  1. 01

    Add a CloneByMe module

    In your scenario, click the + and search for CloneByMe. Pick any of its modules, then click Create a connection. A connection is your CloneByMe account linked to Make once, and every CloneByMe module reuses it afterward.

  2. 02

    Name the connection

    This step is optional, but worth it. A clear name like the agent or workspace it belongs to saves you guessing later, when you have several accounts connected to the same Make organization.

  3. 03

    Authorize and save

    Depending on what CloneByMe asks, either approve Make on the CloneByMe page that opens, or paste the key the app gives you. Then click Save, and Make can start listing what your account contains.

First scenario

Your first scenario with CloneByMe

GoalWhen a question lands in another app, Make gets an answer from your CloneByMe agent and sends it back through CloneByMe.

  1. 01

    Create the scenario

    Open the Scenarios page and create a new scenario. Click the + and add the module of the app where questions arrive, for example the trigger of your form tool. It starts the flow.

  2. 02

    Ask the agent

    Click the + on the right of that first module and search for CloneByMe. Choose Get Agent Response, click Create a connection, then map the question from the previous module into its fields.

  3. 03

    Send the reply

    Add Send Response after it with the same connection. Map the answer that Get Agent Response returned. Make offers the data of earlier modules in a list, so you click rather than type.

  4. 04

    Test with Run once

    Click Run once and trigger a real question. Each module shows the bundles it received: a bundle is one item passed from a module to the next. Check the answer before going further.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs.

Triggers

What can start a CloneByMe scenario?

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

CloneByMe1Watch Events

Watch Events

triggerIn the docs only

Watch Events picks up what changed in CloneByMe each time Make checks, then runs the rest of the chain, so you stop checking the app yourself. The Make documentation lists it without saying which events it covers, which means your first test tells you what really comes through.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, so nothing moves between two checks.
When to use it
you want CloneByMe activity to feed another tool, such as a CRM or a shared sheet.
Watch out
read the bundles after Run once before mapping anything, since the fields depend on what the app sends.
Modules

What can Make do in CloneByMe?

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

CloneByMe1

Get Agent Response

ActionIn the docs only

Your CloneByMe agent's answer, delivered inside the scenario and ready for the next module: judging by its name, that is what this module gives you. The documentation offers no description to confirm it.

When to use it
a question lands in a form or a support inbox and you want the agent's reply without opening CloneByMe.
Watch out
each call counts as one operation, meaning one run of one module, which is what Make counts on your plan.
CloneByMe2

Make an API Call

ActionIn the docs only

Anything the four other modules leave out, you can still reach here: this module calls any endpoint of the CloneByMe API, using the same connection as the rest of your scenario.

When to use it
you need a CloneByMe feature that has no dedicated module in Make.
Watch out
you write the request yourself, and Make's documentation for this app is limited, so know which endpoint you want before you start.
CloneByMe3

Send Response

ActionIn the docs only

With Send Response, the reply leaves through CloneByMe instead of through another tool. That reading comes from the name only, as the documentation describes nothing, so treat your first test as the real check.

When to use it
right after Get Agent Response, when the answer should go out from CloneByMe.
Watch out
this module acts on your real account, so try it with Run once on a harmless case before switching the scenario on.
CloneByMe4

Train Agent

ActionIn the docs only

Keeping your agent up to date without manual uploads is the likely point of Train Agent, which passes new material to CloneByMe from a scenario. Like its neighbors, it has no official description, so the name is the only clue.

When to use it
a new document or answer appears in another app and the agent should learn from it.
Watch out
open the module once the connection exists to see which fields Make really asks for.
Need help

Need help automating CloneByMe with Make?

A person reads every message.

FAQ

CloneByMe and Make: common questions

01Is the CloneByMe Make integration free?
Yes, on the Make side. CloneByMe is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 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 count usage in credits each month. Your CloneByMe subscription is a separate matter that this page does not cover.
02What do you need to connect CloneByMe to Make?
A CloneByMe account and a Make account. The documentation lists no other prerequisite and no official connection steps, so you follow the generic Make flow: add a CloneByMe module, click Create a connection, name it if you like, then either approve Make on the CloneByMe page or paste the key the app provides, and save. The connection is created once and reused by all 5 modules. Once saved, the same connection shows up in the list of every CloneByMe module you add later, so you never authorize twice.
03Does the CloneByMe Make trigger work in real time?
No. Watch Events is a scheduled trigger: Make checks CloneByMe on the scenario's schedule instead of being called the moment something happens. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan. Paid plans let you go down to 1 minute. If you need a faster start, launch the scenario from another app that sends its own trigger. Keep this in mind when you design the flow: whatever you place after Watch Events waits for the next check, not for the event itself.
04What if the CloneByMe module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the CloneByMe API with the connection you already have, so you are not limited to the 4 action modules. Keep in mind that the Make documentation for CloneByMe is flagged as limited: there is little public information about the app, so check the fields each module shows before you rely on them. The module keeps your existing connection, so there is nothing new to authorize before you try it.
05Should you use Make or n8n for CloneByMe?
It depends on where the rest of your automations already live. On Make, CloneByMe offers 5 modules, including a scheduled trigger and Make an API Call, and it works from the Free plan. The same app often has an n8n node as well, so check that it exists before you decide. Neither tool is ranked here: compare the modules each one offers for your case. Picking the tool your team already maintains usually matters more than any single module.
Same platform

Other docs you might need on this stack.

Browse all integrations