Basic actions

Built-in actions are available directly in ChatRex and are not tied to a specific CRM or booking system. The catalog currently contains seven standard actions.

Send webhook

Sends data from the bot to an external system through a webhook. Use it with your own API, an automation platform, or a service that does not have a ready-made integration.

Before configuring the action, define the endpoint, transmitted data, expected response format, and retry rules. Insert integration or bot variables into URL, GET, and POST parameters with @. Never place private keys in the main instruction or another plain-text field.

Stop the bot

Stops automatic processing. Use it to hand a conversation over to a team member, complete a workflow, or prevent further automated replies.

In the prompt, specify the exact stopping condition. If the bot does not have to send a generated response after the action, turn on Do not send a response. By default, this parameter is enabled.

Summarize a conversation

Creates a summary of the conversation. Use it before a handover or in a later automation step so that a team member or another system does not need to read the entire message history.

Describe what the summary must contain, such as the customer's request, contact details, selected products or services, agreed next steps, and unresolved issues.

Dynamic reference list

Stores editable Question–Answer pairs and returns the matching information to the bot. Use it for short rules, status mappings, and frequently changing answers.

1. Add the action Dynamic directory.
2. Select Add row.
3. Fill in the columns Question and Answer.
4. Add the other pairs and save the action.

Send a media file

Sends a file from connected storage. Select a specific file or let the bot choose one based on its description and the user's request.

Before adding the action, upload the files to Media files and provide a clear description for each one. See Use media files for detailed instructions.

Hand over to another bot

Transfers further processing of the current conversation to the selected bot without creating new correspondence. In the action settings, select the receiving bot. Use the action if different bots are responsible for individual topics, products, languages, or service steps.

Describe the transfer criterion and confirm that the receiving bot has its own channels, prompt and knowledge base set up. Avoid cyclical transmission between bots.

Notification in Telegram

Sends a Telegram notification. Use it to alert a team member about a new request, handover, error, or another event that requires a manual response. Insert bot and integration variables with @.

Include only the necessary data in the message and do not send passwords, access keys and other sensitive information.