Integrator — Scenario Dialog Scenarios Hub (Legacy)
Recommended new module: Scenario Builder — modern visual scenario editor that replaces Scenario Dialog. Use Scenario Builder for new development.
A page for integrators creating and editing bot scenarios in Scenario Dialog (legacy). Here you will build dialog scenarios through the visual editor, add translations, and configure bot logic. Below are instructions for each step: creating scenarios, working with sections, adding translations, and import/export.
Quick Overview
High-Level Goals and Scenarios
Creating and Editing Scenarios
Goal — build bot dialog logic through the visual editor.
- Create new scenario — how to create a bot scenario from scratch and configure basic structure. → ./how-to/create-scenario.md
- Edit existing scenario — how to make changes to an already created scenario and update logic. → ./how-to/edit-scenario.md
- Create scenario section — how to organize a complex scenario into separate sections for better structuring. → ./how-to/create-section.md
Working with Nodes and Logic
Goal — configure individual scenario elements and their interaction.
- Add message — how to create a node with message text for the user.
- Configure keyboard — how to add buttons to a message and configure button transitions.
- Add input wait — how to collect data from the user through Input node.
- Use actions in scenario — how to add and configure actions to extend scenario functionality. → ./how-to/use-action-in-scenario.md
- Configure MCP tool parameters in a scenario — how to add input parameters (Input Schema) and use them in messages, conditions, and actions of the section. → ./how-to/configure-mcp-tool-parameters.md
Multilingual Support and Translations
Goal — ensure support for multiple languages in the scenario.
- Add translations to scenario — how to add translations of message texts for different languages. → ./how-to/add-translations.md
- Switch editing language — how to view and edit the scenario for a specific language.
Import and Export
Goal — save a backup copy of the scenario or transfer it between projects.
- Export scenario — how to save the scenario to a file for backup. → ./how-to/import-export-scenario.md
- Import scenario — how to load a scenario from a file and restore its structure.
Version History
Goal — track scenario changes and restore previous versions.
- View and restore scenario versions — how to view version history and activate a previous scenario version. → ./how-to/view-scenario-history.md
Explanation Documents
Goal — understand concepts and principles of working with scenarios.
Actions and Automation
- What are actions and how they work — understanding standard and custom actions, their use in scenarios. → ./explanation/actions-in-scenarios.md
- Using autobroadcast__create action — how to use the action for scheduled broadcasts in scenarios. → ./explanation/autobroadcast-action-usage.md
- Displaying images to user — ways to send images through UI and send_photo action. → ./explanation/display-image-to-user.md
- Email categorization — automatic categorization of incoming emails using AI. → ./explanation/email-categorization.md
Formatting and Styling
- HTML text formatting — using HTML tags to style text in Telegram and Widget. → ./explanation/html-text-styling.md
- Inline keyboard — configuring inline keyboard for Telegram and Widget. → ./explanation/inline-keyboard.md
- Viber keyboard styling — configuring appearance of keyboard buttons in Viber. → ./explanation/viber-keyboard-styling.md
- Viber start message — features of working with the first message in Viber. → ./explanation/viber-start-message.md
Integrations and External Systems
- Telegram WebApp — opening web applications directly in Telegram. → ./explanation/telegram-webapp.md
- Payment via bot — integration with payment systems (Liqpay, Apple Pay, Google Pay). → ./explanation/payment-via-bot.md
- Corezoid integration — connecting operator panel to Corezoid via webhook. → ./explanation/corezoid-integration.md
- Telegram group bots — creating bots that listen and respond in Telegram groups. → ./explanation/telegram-group-bots.md
- Facebook Ads referral tags — tracking traffic source from advertising campaigns. → ./explanation/facebook-ads-referral-tags.md
- Launching scenario from Facebook Ads — configuring unique scenarios for different advertising campaigns. → ./explanation/facebook-ads-scenario-launch.md
Operator Functions
- Configuring alias for outgoing dialog — controlling user behavior after dialog completion. → ./explanation/outgoing-dialog-aliases.md
- Copying scenario — translating scenario to other languages while preserving structure. → ./explanation/copy-scenario.md
Where to Work in the Interface
Main work with scenarios happens in the Dialog module:
Dialogmodule:Apps -> Dialog— here you edit bot scenarios.- Route
/dialog/bot-scenario/:id: opens the scenario editor for a specific bot. - Sections panel: at the top of the screen — for switching between scenario sections.
- Canvas: central area — for visual editing of nodes and connections.
- Right panel (RightSideBar): for editing parameters of the selected node.
- "Save" button: at the bottom of the screen — for saving changes to the scenario.
Quick Links
Creating and Editing
Multilingual Support
Import and Export
Version History
MCP and AI Assistants
- How to connect an AI assistant to a scenario via MCP
- Calling scenario sections from AI assistants (MCP)
- Configure MCP tool parameters in a scenario
Explanation Documents
Actions and Automation
- What are actions and how they work
- Using autobroadcast__create action
- Displaying images to user
- Email categorization
Formatting and Styling
Integrations and External Systems
- Telegram WebApp
- Payment via bot
- Corezoid integration
- Telegram group bots
- Facebook Ads referral tags
- Launching scenario from Facebook Ads