# Cloud BOT integrations: bots and jobs

> Import a bot, run a bot and upload a file in Cloud BOT, and start a workflow when Cloud BOT sends “Bot execution finished”.

**Canonical page:** https://tray.ai/connectors/cloud-bot-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Cloud BOT is a no-code browser automation service from C-RISE that records web tasks as bots, runs them in the cloud and returns the data they collect. Tray.ai connects to Cloud BOT through the HTTP Connector, so your workflows can call the Cloud BOT API alongside the rest of your stack.

## Use cases

### Bots

Read, create, and delete bots in Cloud BOT from any Tray.ai workflow. The Cloud BOT API covers calls such as list bots and get bot details.

- List bots
- Get bot details
- Export a bot

### Jobs

Read, create, and update jobs in Cloud BOT from any Tray.ai workflow. The Cloud BOT API covers calls such as run a bot and list bot jobs.

- Run a bot
- List bot jobs
- Get a job

### Subscriptions

Read and update subscriptions in Cloud BOT from any Tray.ai workflow. The Cloud BOT API covers calls such as list bot subscriptions and subscribe to a bot.

- List bot subscriptions
- Subscribe to a bot
- Unsubscribe from a bot

### Files

Read and create files in Cloud BOT from any Tray.ai workflow. The Cloud BOT API covers calls such as upload a file and download a file.

- Upload a file
- Download a file

## Challenges Tray.ai solves

### Keeping Cloud BOT credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Cloud BOT credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Cloud BOT API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Cloud BOT API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Cloud BOT?

Yes. Tray.ai connects to Cloud BOT through the HTTP Connector, which calls the Cloud BOT API directly. Any call the Cloud BOT API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Cloud BOT?

The Cloud BOT API uses an API key in a request header and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Cloud BOT connector?

Cloud BOT runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Cloud BOT connector from the Cloud BOT API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/