How the process library works

The process library is a list of all bots (processes) in ConnectiveOne. Here you quickly find the scenario you need, see its triggers and status without opening the editor, and go straight to editing. This page explains how the library works, filters, categories, and hierarchy.

What is Process Library and how it relates to the bots list

Process Library (/process_library) is the new interface for the same thing: the list of bots and their settings. In terms of data, it is the same as Settings → Bots (/settings-page/bots), but with an improved UI.

New interface: Process Library — main menu item. Opens /process_library with filters, cards, categories, tags, hierarchy, and search.

Deprecated: Settings → Bots (/settings-page/bots). Bot settings — /settings-page/bot-settings/:id.

Process Library routes:

/process_library — bots list
/process_library/:id — bot settings

Permissions: same as for bots — view and edit.

In the Constructor hamburger menu (top bar), the Process menu block does not open the library page — it selects the active process for your session. After you choose a bot, the page reloads and modules run in that bot's context.

	Process menu (hamburger)	Process library
Where	Global menu in the top bar	`/process_library` or tab in Scenario Builder
Purpose	Quickly switch the active bot	Find bots, cards, filters, open the editor
Search	By name in processes available to you	By name, description, tags, categories, triggers
Pinning	Star — personal list in the browser	—

→ Switch the active process in the main menu

Context and the problem

A company can have many bots: different scenarios for channels, automation rules, communication scenarios. Switching between sections and searching through long lists takes time. Without a single place, it's hard to understand which bot does what and how to open it quickly.

What the process library solves:

All bots in one place — no need to remember where everything is
Filters and search — find by category, tag, trigger
Information on the card — triggers, tags, run count visible without opening
Single context — library and editor together

Typical use cases:

Find a bot for editing by name or category
See which triggers are configured without opening the scenario
Organize bots by categories and tags
Create a child process from an existing one

Key concepts

Process cards

Each process (bot) is displayed as a card. On the card you see:

Name — click opens the constructor
Description — short description (if any)
Triggers — how the process starts (channel, webhook, internal event)
Tags — for grouping and search
Run count — how many times the process ran
Updated at — when it was last changed

From the card you can click "Open constructor" and go straight to editing the scenario.

Filters

Search — by name or description. Enter part of the text — the list updates.

Status — active or inactive. Inactive processes don't run.

Process type:

Process — sequence of actions for business process automation
Automation rule — rule that runs under certain conditions
Communication scenario — dialog with clients via channels (chat bots)

Category — group the process belongs to (e.g. "Support", "Sales"). Categories are configured separately.

Tags — free labels for search and grouping. You can select multiple tags — processes with at least one of them are shown.

Triggers — filter by launch type: channels (Telegram, Viber, Widget, etc.), webhook, internal events.

Hierarchy (parent and child processes)

Processes can be nested: one process is parent, others are children. This helps organize complex scenarios: main bot and sub-scenarios.

Parent process card shows the number of children
Children can be collapsed/expanded
From context menu you can create a child process or detach from parent

Sorting

The list can be sorted by:

name (alphabetical)
creation date
last edit date
run count
ID

How it works together

You open a Process Library via Menu → Scenario Builder or the "Process Library" tab.
Apply filters if needed: category, tags, triggers, status.
Search by name or description.
Click the process name or "Open constructor" — the scenario editor opens.
After editing, return to the library — context is preserved.

Single context: Library and editor are parts of one module. No need to switch between sections.

Why a library

Alternative: separate bot lists in different sections, search through settings. This scatters attention and complicates navigation.

Library:

Gathers all processes in one place
Allows filtering by various criteria
Shows key information on the card — no need to open each scenario
Supports hierarchy for complex structures

Implications for users

For those working with scenarios:

Use categories and tags — easier to find the right bot
Add descriptions to processes — search works by description too
Triggers on the card help quickly understand how the bot starts

Common mistakes:

Forgot about filters — with many processes, apply category or tag first
Not using hierarchy — for complex scenarios with sub-scenarios, child processes simplify structure

How-to: Switch the active process in the main menu
How-to: How to use the process library
Explanation: How the scenario editor works
Learn: Processes and Scenarios — Scenario Builder
How-to: Create scenario