Connect to Operator Node Parameters

The Connect to Operator node (action_operator_panel__connect_to_operator_with_msg) creates a chat room and connects the client to an operator. After execution, the dialogue is displayed in the Operator Panel. In Node Inspector (right panel) the following sections are available:

Where the form comes from

Inspector fields and grouping are built from the action json_config in Action Jail (parameters, ui.groups, and optionally events_schema). For AI agents: do not invent parameter names — use the live form or the technical action doc: docs/developer/engine/actions/operator_panel__connect_to_operator_with_msg.md.

Canvas events (scenario branches)

After the action runs, the engine returns one branch. On the canvas these are separate outputs from the node (order follows the events schema). Typical set:

Event (branch)When it happens
successChat created; user connected to an operator
bannedUser is banned (active ban)
limitNo operators available (capacity)
errorChat creation failed or other execution error

Connect each branch to the next nodes (separate edges). These are not the same as add_button / add_return_button (see below) — those configure extra UI in the chat; events describe execution outcome.

Basic Settings

  • Request subject (subject_alias) — subject under which the chat is created (selection from configured subjects).
  • Auto-connect (auto_connect_operator) — whether to automatically connect a free operator.
  • Assigned operator (assigned_operator) — specific operator (when auto-connect is not used).
  • Tags (tag_ids) — tags added to the request when connecting.

Buttons in chat (JSON parameters)

  • Add button (add_button) — add a close-chat style control in the operator chat context (texts from bot constants).
  • Add return button (add_return_button) — return-to-bot button (text from constants).

These are service UI options, not the canvas events in the table above.

Timeouts

  • Transfer timeout (transfer_timeout) — how many seconds to wait for operator response before automatic transition (if configured).

Messages

  • Text to operator (customTextToOperator) — message the operator sees when connecting (dialogue context, summary, etc.).

Transition aliases (stored in state constants)

Alias fields define where the scenario goes on certain chat lifecycle events. Examples:

  • chat_closed_alias — when the chat is closed (per product rules).
  • alias_return_scenario — when the user taps the return button (if add_return_button is enabled).
  • Others as in the full action config: chat_closed_by_timeout_alias, connection_timeout_alias, chat_closed_by_client_alias — see the Engine action doc.

They complement normal canvas edges (success / banned / limit / error), not replace them.