# BotStar integrations: bots and bot attributes

> Create a bot, create a bot attribute and create an entity in BotStar. Connect BotStar to the rest of your customer service stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/botstar-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

BotStar is a chatbot and live chat builder for websites and Facebook Messenger, with a visual flow editor and a built-in CMS for bot content. Tray.ai connects to BotStar through the HTTP Connector, so your workflows can call the BotStar API alongside the rest of your stack.

## Use cases

### Bots

Read and create bots in BotStar from any Tray.ai workflow. The BotStar API covers calls such as list bots and get a bot.

- List bots
- Get a bot
- Create a bot

### Bot attributes

Read, create, update, and delete bot attributes in BotStar from any Tray.ai workflow. The BotStar API covers calls such as list bot attributes and create a bot attribute.

- List bot attributes
- Create a bot attribute
- Update a bot attribute

### Users

Read, create, and update users in BotStar from any Tray.ai workflow. The BotStar API covers calls such as get user info and update user attributes.

- Get user info
- Update user attributes
- Create custom user attributes

### CMS entities

Read, create, update, and delete cms entities in BotStar from any Tray.ai workflow. The BotStar API covers calls such as list entities and create an entity.

- List entities
- Create an entity
- Update an entity

### CMS entity items

Read, create, update, and delete cms entity items in BotStar from any Tray.ai workflow. The BotStar API covers calls such as list entity items and create an entity item.

- List entity items
- Create an entity item
- Update an entity item

## Challenges Tray.ai solves

### Keeping BotStar 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 BotStar 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 BotStar 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 BotStar 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 BotStar?

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

### How does Tray.ai authenticate with BotStar?

The BotStar API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated BotStar connector?

BotStar runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated BotStar connector from the BotStar 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/