Cloud BOT Zapier integrationAutomate Cloud BOT with Zapier.
The Cloud BOT Zapier integration gives you 1 trigger, 3 actions and 0 searches. Enough to start a cloud browser robot from another app, react the second it finishes, and push files in or pull them out, all without opening the Cloud BOT dashboard.
Verified Trustpilot reviews · AI, automation & growth agency
What the Cloud BOT Zapier integration actually does
Cloud BOT is a browser automation service: you create your own robot, and it runs in the cloud whenever you call it. Connecting it to Zapier means another app can launch that robot, and the end of a run can set off work elsewhere. You stop babysitting the robot. The rest of your tools hand it jobs and pick up after it.
Three results worth building. A robot that runs when a row lands. A new line in a spreadsheet feeds Execute BOT, with the row values passed as the robot's inputs. A team that hears about a finished run. BOT Done fires the moment a robot stops, and the next step posts to a chat channel or opens a card. Files that travel without you. Upload File drops a document into Cloud BOT and hands back its reference; Download File does the reverse when you give it a reference.
Now the limits, because the editor won't spell them out. There is no search step for this app, so a Zap can't look up an existing robot or file by name: you pick them in the step or type the reference. There is only one trigger. Nothing fires when a robot starts, fails halfway, or when a file appears; you only hear about the end of a run. And the API has to be switched on in your Cloud BOT account before any action works (Execute BOT also wants the robot published).
If you are still choosing a platform, the Cloud BOT Make integration page covers the same app on Make, and the Make vs Zapier comparison sets the two tools side by side.
Zapier vocabulary, one line each
Seven words you'll meet in the editor. Read them once and the rest of the page reads faster.
- Zap
- A trigger plus at least one action. With Cloud BOT, a robot that has just finished its run is the natural place to start one.
- Trigger
- The event that starts a Zap. Here, a Cloud BOT robot finishing its run. Once the Zap is on, Zapier waits for it.
- Action
- The step that acts once the Zap has started. For this app, that means launching a robot, or pushing a file in or pulling one out.
- Task
- Zapier's billing unit. Each Cloud BOT action that succeeds is one task; BOT Done firing is never counted on your monthly allowance.
- Polling vs instant
- Polling means Zapier asks the app on a timer. Instant means the app reports the event itself, which is how BOT Done reaches Zapier.
- Filter
- A checkpoint after the trigger: the Zap carries on only when the finished run meets your rule, so empty runs stop right there.
- Connection
- Your Cloud BOT login saved in Zapier once. BOT Done and all three actions reuse it, so you never sign in again per step.
What a Cloud BOT Zap really costs
No premium badge here: Cloud BOT runs on Zapier's free plan. Robots finishing cost you nothing; only actions that succeed show up on the bill.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps only
- Trigger cost0 tasks
- Each successful action1 task
BOT Done costs nothing, however many robots finish. Each action that succeeds counts as one task, so a Zap that runs a robot and then downloads a file uses two per run. An action that fails isn't counted. The free plan gives 100 tasks a month but only two-step Zaps: one trigger, one action. Add a filter or a second action and you need a paid plan. The interval grid below applies to polling triggers only; BOT Done is instant, so it ignores it.
Connect Cloud BOT to Zapier in three steps
- 01
Open your connections
From the Apps page of your Zapier account, hit + Add connection. Have your Cloud BOT login at hand, plus access to any robot or contract a colleague owns that the Zap should use.
- 02
Find Cloud BOT
Search for Cloud BOT in the dialog, click it in the results, and confirm with Add connection. Zapier then sends you to Cloud BOT in a fresh tab. Pick the right account if you run more than one.
- 03
Sign in and allow access
Log in to your Cloud BOT account in that tab and grant Zapier access. The connection then shows up in every Cloud BOT step, so you only do this once per account.
Your first Zap: hand a scraping run to a second robot
GoalAn online shop runs one Cloud BOT robot that reads competitor product pages. When it finishes with something worth acting on, a second robot updates prices in the shop's back office.
- 01
Build: pick BOT Done
Create a Zap, choose Cloud BOT and the BOT Done event. Set Language, Contract and the robot that reads competitor pages, so only its runs start the Zap.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items from the account. Look at what the robot returned and spot the value that tells a useful run from an empty one.
- 03
Add the filter
From the plus icon, add Filter. Point it at the value you spotted, pick a rule of the right type (text or number), and type what to compare with.
- 04
Add Execute BOT
Pick Cloud BOT, then Execute BOT. Choose the price-update robot (never the one BOT Done watches), set Async, and map the values it needs as inputs.
- 05
Test, then publish
Test the action once and check the second robot actually ran in Cloud BOT. Then click Publish. With the filter this is a multi-step Zap, so it runs on a paid plan.
The Cloud BOT trigger
1 event starts a Zap when something happens in Cloud BOT, and one of them is instant: the app calls Zapier straight away, whatever your plan.
BOT Done
Instant triggerIn Zapier“Triggers when a BOT at the end of execution.”
Starts your Zap as soon as one of your Cloud BOT robots reaches the end of its run. You choose which robot to watch, along with its Language and Contract, so other robots on the account don't set it off.
The 3 Cloud BOT actions
Cloud BOT gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Download File
ActionIn Zapier“Download a file. You can set file ref and get file contents.(The API must be enabled on Cloud BOT website.)”
Pulls a file out of Cloud BOT when you hand it the file's reference, and gives its contents to the next step of the Zap.
Execute BOT
ActionIn Zapier“Execute your BOT. You can set specific input values for your BOT. (The API must be enabled and the BOT must be published on Cloud BOT website.)”
Launches one of your robots from any trigger, with input values you set or map from earlier steps, so the same robot can handle a different page or account each time.
Upload File
ActionIn Zapier“Upload a file. You can set file contents and get file ref.(The API must be enabled on Cloud BOT website.)”
Sends a file into Cloud BOT under the name you choose and returns a reference you can reuse further down the Zap.
When a Cloud BOT Zap breaks
No Zapier help article is tied to Cloud BOT. The cases below combine Zapier's general behaviour with what each Cloud BOT action demands before it will run.
Most problems show up on the first test or the first busy day. If a Zap still misbehaves after these checks, the Zapier troubleshooting page walks through the general method.
The API is off or the robot unpublished
Every action depends on the API being enabled on the Cloud BOT website, and Execute BOT also needs a published robot. Check both before blaming the Zap.Runs from before the Zap are ignored
A Zap only reacts to what happens after you publish it. Robots that finished yesterday never reach BOT Done, so move that backlog by hand.A robot that restarts itself
If BOT Done watches a robot and Execute BOT launches that same robot, every end starts a new run. The loop burns through your task count fast.A sudden burst held back
When a huge batch of runs ends at once, after a bulk job for example, Zapier's flood protection can hold the trigger back instead of firing for each one.
Need help automating Cloud BOT with Zapier?
A person reads every message.
