> For the complete documentation index, see [llms.txt](https://docs-conversational-ai.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/administration/bots-configuration.md).

# Bots Configuration

## Purpose

Register Syntphony Conversational AI bot integrations so they can be selected as routing destinations when you configure sources.

## Who this is for

Administrators and technical operators with access to Syntphony Conversational AI and Messaging Portal administration.

## Prerequisites

* Administrative or supervisor-level access to the Messaging Portal.
* Access to your Syntphony Conversational AI organization and environment.
* Required organization, environment, and bot identifiers collected before you start (see table below).

## Steps

1. Open your Syntphony Conversational AI portal and collect the required values.
2. Validate and prepare these variables:

| Variable                                                    | Description                                                                                            | Note                        |
| ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ | --------------------------- |
| **Organization variables**                                  |                                                                                                        |                             |
| Organization name                                           | Name of the organization in Syntphony Conversational AI                                                |                             |
| Organization keycloak URL                                   | Obtain from login flow in browser developer tools (example: `https://keycloak-americas-admin.eva.bot`) | `https` prefix required     |
| Organization UUID                                           | Found in the URL after logging in                                                                      |                             |
| **Environment variables**                                   |                                                                                                        |                             |
| Environment client ID                                       | Found in the Environments section                                                                      |                             |
| Environment secret (Syntphony Conversational AI secret key) | Provided when the organization is created (request from NTT team if needed)                            |                             |
| Environment API key                                         | Shown in the environment details under API key                                                         |                             |
| Environment UUID                                            | Shown in the environment selector as environment key                                                   |                             |
| Environment instance                                        | Request from NTT team (example: `api-americas-instance1.eva.bot`)                                      | `https` prefix not required |
| **Bot variables**                                           |                                                                                                        |                             |
| Bot UUID                                                    | Found in the bot URL                                                                                   |                             |
| Channel UUID                                                | Found in the bot integrations section                                                                  |                             |

3. In the Messaging Portal, open **Administration** and go to **Bots Configuration** (Syntphony Conversational AI configurations).
4. Select **New configuration**.
5. Fill the configuration form (required fields are marked with an asterisk).
6. Save the configuration.

<figure><img src="https://3261478287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXHkoH2WwcemdqskPI0KI%2Fuploads%2FnaDPLPGTKJIPrflE51a9%2Fimage.png?alt=media&amp;token=cf08359e-e2d8-494f-ae9e-af9a06b889ba" alt=""><figcaption><p>Bot integration configuration</p></figcaption></figure>

## Validation

* The bot appears as an available destination when you create or edit a source in [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md).
* Linked environment and bot UUIDs match the values from Syntphony Conversational AI.

## Expected outcome

Bot integrations are registered and ready to be linked in [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md).

## Related pages

* [Administration](/syntphony-messaging-portal/messaging-tools/administration.md)
* [Source Configuration](/syntphony-messaging-portal/messaging-tools/administration/source-configuration.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs-conversational-ai.syntphony.com/syntphony-messaging-portal/messaging-tools/administration/bots-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.