Built-in actions reference for scenarios

Page type: Reference.

Built-in actions are supplied by ConnectiveOne and its modules, including Operator Panel, Custom Data, Registered Users, and Fastline. You do not create them in Action Jail: add an Action node and select the function in Node Inspector.

Full catalog: Actions reference. Below are the most common groups with typical parameters and return values.

Contents

1. Constants (set)
2. Routing (goto_alias, switch, clear_constant)
3. Operator handoff
4. Registered users (registered_users__*)
5. Custom Data (custom_modules__*)
6. Schedule (check_schedule)
7. Conditional logic (if_else)
8. Timers (sleep, interval__*)
9. Media (send_photo, send_video, send_file)
10. User input (get_user_input)
11. Fastline / AI
12. Analytics (statistic__set)

1. Constants (set)

Purpose: write values into scenario state (language choice, registration fields, API results).

Template node: often Set (action_set) — see Set node and Set parameters.

Built-in set action: key-value json_obj with {{placeholder}} support.

Return: typically default → next node.

2. Routing (goto_alias, switch, clear_constant)

vs Router node: Router works with request-context fields (channel, status, tags…) in the visual inspector. switch is for branching on scenario constants / variables and expressions in an Action node (common in JSON / imported flows).

Typical switch exits: the first true condition → matching event (object key); on expression parse failure → error.

Important (pitfalls):

1. No built-in default branch. If no condition is true, the action returns nothing — the scenario can go silent. Add a last fallback key (e.g. fallback) with a always-true condition: "1 == 1", and wire that edge on the canvas.
2. String comparisons need quotes on both sides. After placeholder substitution the expression must stay valid. Wrong: {{user_choice}} == 'sales' (becomes sales == 'sales' and yields error). Correct: '{{user_choice}}' == 'sales'.

Example Action switch params:

{
  "sales": "'{{user_choice}}' == 'sales'",
  "support": "'{{user_choice}}' == 'support'",
  "other": "'{{user_choice}}' == 'other'",
  "fallback": "1 == 1"
}

→ Router parameters · Conditional branches (Router)

3. Operator handoff (operator_panel__connect_to_operator_with_msg)

Docs: Connect to operator node, Parameters, Connect chat to operator.

Returns: success, banned, error.

4. Registered users (registered_users__*)

Actions: registered_users__check_phone — normalize/validate phone; registered_users__set — save/update profile; registered_users__get — find customer by chat or phone.

Phone: when collecting a number in the scenario — run registered_users__check_phone first, then __set. __set does not normalize 050… → 380….

After registered_users__get success: read standard fields as {{client.first_name}} (not {{registration:first_name}} with a colon). Details: registered_users__get.

Details: Actions reference — Registered Users.

5. Custom Data (custom_modules__*)

How-tos: custom_modules__get, custom_modules__set, patterns.

6. Schedule (check_schedule)

Parameters: morning_time, evening_time, weekends, timezone.

Returns: success / error.

7. Conditional logic (if_else)

Structure: if / elseif / else with event names.

See also: Actions in scenarios.

8. Timers (sleep, interval__*)

9. Media (send_photo, send_video, send_file)

Details: Display image to user.

10. User input (get_user_input)

For group bots and mention handling; outputs raw_input, bot_mentioned, no_input.

11. Fastline / AI

Configure agents in FastlinePro module; scenario parameters depend on Action Jail config.

12. Analytics (statistic__set)

Event recording for statistics — see actions reference.

Summary