SQL Databases

Admin

Database used by admin application. It stores information that is available through GUI like users, project configurations, flow diagram, NLU training phrases and knowledge base.

Analytics

Every message that is processed by Automate platform is stored in this database. It holds diagnostic information (timing and errors) on each bot turn as well as whole conversation transcript. Only analytics service connects directly to this database.

⚠️ Please be aware that with a big volume of conversation, this database may get big and therefore slow. However, this should not affect bot runtime latency as long as you are not calling system.lastConversations in the flow.

📘

Monitoring bot performance ⏰

This database can be queried to monitor the performance of the platform. Please read the tutorial on performance monitoring and troubleshooting for more details.

Cron orchestrator

Cron orchestrator application stores in this database information about periodic jobs and the results of such jobs. These jobs are mostly internal for example deleting expired conversations to comply with retention policy however some jobs are configurable like exporting to warehouse

Dialog manager

This database holds information on current ongoing sessions, published flows and integrations.

⚠️ As it is solely used by the dialogs service the performance of this database is critical in terms of bot latency.

NLU facade

The NLU facade application is a facade for other NLU services through which the dialog service gathers results of detected intents and variables. In this database NLU settings are stored as well as dictionaries for autocorrect mechanism.

SSO

Database to hold information on authentication done by the sso service

Storage

Storage service keeps in this database information about saved recordings. By default it holds metadata information, but it can also keep whole binary files if it is configured to do so.

⚠️ If you are using PostgreSQL as a storage service, it might get bulky. Please refer to the service documentation for more details.

Thread coordinator

In this database, information about the owner application of conversations is stored. This data is managed by the thread coordinator service as is used when conversations are redirected to human agents .

Web chat

This database is used by the webchat service it holds information about webchat configurations and conversations which include both bot and agent sessions.

Chimeo

Database used by the SentiOne Listen&React applications which is a legacy & redundant integration, not present in newer deployments.

Voice Gateway

Charon

Configuration regarding voice gateway integrations that is set through Channels Connector in Admin UI. This schema is used by charon service that is responsible for SIP integration.

Crocotta

Crocotta service that is responsible for managing TTS services holds its configuration and events in this database schema.

Gall

Call recorder application called gall keeps information about the recordings and their status.

Qpido

Qpido is a dialer service used for phone outbound campaigns. This database schema hold information about contacts, campaigns and call attempts.