# Bot9 integrations: bots and conversations

> Update a bot, update a chat and create a note in Bot9. Connect Bot9 to the rest of your customer service stack with Tray.ai.

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

## Overview

Bot9 is a no-code AI chatbot builder from Dukaan that trains a support bot on a company's own content and hands conversations to human agents when needed. Tray.ai connects to Bot9 through the HTTP Connector, so your workflows can call the Bot9 API alongside the rest of your stack.

## Use cases

### Bots

Read and update bots in Bot9 from any Tray.ai workflow. The Bot9 API covers calls such as get bot details and update a bot.

- Get bot details
- Update a bot

### Conversations

Read and update conversations in Bot9 from any Tray.ai workflow. The Bot9 API covers calls such as list chats and get chat messages.

- List chats
- Get chat messages
- Update a chat

### Conversation notes

Read and create conversation notes in Bot9 from any Tray.ai workflow. The Bot9 API covers calls such as create a note and list notes.

- Create a note
- List notes

### Contents

Read, create, and update contents in Bot9 from any Tray.ai workflow. The Bot9 API covers calls such as create content and list contents.

- Create content
- List contents
- Update content

## Challenges Tray.ai solves

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

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

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

The Bot9 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 Bot9 connector?

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