Resources · Make integration

Cloud BOT Make integrationAutomate Cloud BOT with Make.

Can Make start your Cloud BOT runs and handle the files around them? The Cloud BOT Make integration offers 5 modules: 1 trigger and 4 actions. This guide is for operations teams who run BOTs and want the steps before and after them handled for them, starting with a simple first scenario.

Try the Cloud BOT integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cloud BOT Make integration do?

The Cloud BOT Make integration links your Cloud BOT account to Make, a no-code tool where you build a scenario (the automation itself, a chain of bricks called modules). Once linked, Make can launch your BOTs, send them files, fetch files back and notice when a BOT has finished its work.

Pick up results as soon as a run is over. Watch BOT Done starts the scenario when a BOT has completed, then Download File retrieves what it produced so the next module can store it or share it with the right person.

Feed a BOT, then set it going. For a finance team, a file coming from another app goes to the BOT through Upload File, and Execute BOT launches the run right after. Nobody has to open Cloud BOT to start it by hand.

Reach the rest of the API. The Make documentation points to the Cloud BOT API for the full list of endpoints; Make an API Call reaches them with the connection you already created.

A limit worth knowing: the documentation lists the modules without describing them, so the exact fields only appear once you open each module in Make. If you are still weighing your options, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains how operations are counted. Stuck on a run that fails? See Make troubleshooting.

Connect

How do you connect Cloud BOT to Make?

  1. 01

    Allow external connections in Cloud BOT

    In your Cloud BOT account, open Connect in the left sidebar. Turn on the switch in External Connections, then, under BOT to connect, turn on the switch of each BOT that Make should be able to reach.

  2. 02

    Create the connection in Make

    Add any Cloud BOT module to your scenario and click Create a connection. A connection is your Cloud BOT account linked to Make once, then reused by every Cloud BOT module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Save and approve access

    Click Save. If Cloud BOT asks you to sign in and confirm access, do it in the window that opens. Only teams with their own custom app need Show advanced settings, where they paste their client credentials.

First scenario

Your first scenario with Cloud BOT

GoalWhen a BOT finishes in Cloud BOT, Make downloads the file it worked on.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor to add your first module.

  2. 02

    Add the trigger

    Search for Cloud BOT, choose Watch BOT Done and click Create a connection if your account is not linked yet. Then fill in the fields Make shows for this module.

  3. 03

    Fetch the file

    Click the + to the right of the trigger and add Download File. Map the data coming from Watch BOT Done into its fields so Make knows which file to pull.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time; open the bubble above each module to read the bundles it received, a bundle being one item passed from one module to the next.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks Cloud BOT (every 15 minutes by default), then switch the scenario on so it keeps running without you.

Triggers

What starts a Cloud BOT scenario

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

Cloud BOT1Watch BOT Done

Watch BOT Done

triggerIn the docs only

Watch BOT Done gives you a scenario that starts once a BOT has completed, so whatever comes next happens without anyone checking the Cloud BOT dashboard. The Make documentation gives no description of it, so read the fields in the module before relying on it.

How it fires
this is a scheduled trigger, going by its name: Make checks the app on the scenario's schedule, every 15 minutes by default, and at least 15 minutes apart on the Free plan.
When to use it
when a finished run should lead to a follow-up step, such as downloading its output or alerting a colleague.
Watch out
the scheduled type is deduced from the name, so click Run once and look at the bundles it returns before building on it.
Modules

Everything the Cloud BOT modules can do

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

This app uses webhooks to trigger a scenario when an event occurs instantly. All webhook modules have an instant tag next to their name. When you create a Cloud BOT webhook in Make, it is attached automatically and requires no additional set up.

Cloud BOT1

Execute BOT

ActionIn the docs only

Execute BOT lets a scenario launch one of your BOTs itself, which removes the manual start from the process. It is an action, so it works on one item each time it runs.

When to use it
after Upload File, once the BOT has the file it needs, or when a record created in another app should set a run going.
Watch out
Make only reaches the BOTs switched on under BOT to connect in Cloud BOT.
Cloud BOT2

Upload File

ActionIn the docs only

Upload File sends a file from your scenario to Cloud BOT, so the BOT finds its input ready instead of waiting for someone to drop it in. The file usually comes from an earlier module in the flow.

When to use it
when an attachment or export produced elsewhere is the raw material of a BOT run.
Watch out
on the Free plan, Make handles files of up to 5 MB, and 512 MB of data transfer in total.
Cloud BOT3

Download File

ActionIn the docs only

Download File brings a file from Cloud BOT back into the scenario, where the next module can store it, attach it to an email or pass it to another tool. This is how a BOT's output leaves Cloud BOT without a manual export.

When to use it
right after Watch BOT Done, to collect what the run produced.
Watch out
the same Free plan file size limit of 5 MB applies to what you pull.
Cloud BOT4

Make an API Call

ActionIn the docs only

Make an API Call gives you access to any Cloud BOT API endpoint, using the connection you already set up, for everything the four other modules do not cover. It suits readers comfortable with an API reference.

When to use it
when the operation you need appears in the Cloud BOT API documentation but has no dedicated module in Make.
Watch out
you write the request yourself, so check the endpoint and method in the Cloud BOT API documentation first.
Need help

Need help automating Cloud BOT with Make?

A person reads every message.

FAQ

Common questions about Cloud BOT and Make

01Is the Cloud BOT Make integration free?
Yes, Cloud BOT is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files of 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 40 minutes of execution. Your Cloud BOT subscription is a separate matter, handled on the Cloud BOT side.
02What do you need to connect Cloud BOT to Make?
A Cloud BOT account and a Make account. The documentation lists no other prerequisite. On the Cloud BOT side, open Connect, turn on External Connections and switch on each BOT that Make should reach under BOT to connect. In Make, click Create a connection on any Cloud BOT module, name it if you like, click Save and confirm access when asked. Teams with their own custom app add their client credentials under Show advanced settings.
03Does the Cloud BOT trigger in Make react in real time?
No. Watch BOT Done is listed as a scheduled trigger, a type inferred from its name since the documentation does not describe it. Make checks Cloud BOT on the scenario's schedule: every 15 minutes by default, never less than 15 minutes apart on the Free plan, and down to 1 minute on paid plans. The documentation mentions webhook modules with an instant tag, but none appears in the current module list for this app.
04What if a Cloud BOT module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Cloud BOT API with the same connection as the other modules, so an operation without its own module is still within reach. The Cloud BOT API documentation lists the available endpoints. Beyond the app itself, the Free plan limits still apply to such calls: 5 MB per file, 512 MB of transfer and 5 minutes of execution per run.
05Should you use Make or n8n for Cloud BOT?
It depends on the criteria that matter to your team. On the Make side, Cloud BOT offers 5 modules, including one trigger and Make an API Call for the rest of the API, all usable from the Free plan. Many apps also have an n8n node, so check whether one exists for Cloud BOT, then compare the modules each tool offers against the steps you need to automate. The n8n vs Make comparison on this site lays out those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations