System Operator Library¶
The system operator library contains the platform’s built-in processing operators for selecting operator types and versions in workflow nodes. It is located in the system catalog in Catalog and is read-only.
System Operator List¶
System operator |
Purpose |
|---|---|
Document Parsing |
Parse document files |
Image Parsing |
Parse images |
Audio Parsing |
Parse audio |
Video Parsing |
Parse video |
Chunking |
Split text |
Text Embedding |
Generate vectors |
Cleansing |
Clean data |
Information Extraction |
Extract structured information |
Dataset Generation |
Generate datasets |
Open an operator’s details in Catalog / system catalog to view its type, current version, creation and update information, description, input / parameter / output definitions, and version history (version number, date, and change description; the current version is highlighted).
Versions and Workflows¶
A workflow node can be pinned to an operator version. When the platform upgrades a system operator, the behavior of workflows bound to an existing version remains unchanged.
To use new behavior, explicitly switch the version on the node and perform regression testing.
After an operator is imported to the agent side through a snapshot, it can appear as a tool. See the Glossary for the concept.
Custom Operators (Boundary)¶
The system library cannot be modified. Place business-specific operators in a regular Catalog directory:
Method |
Description |
|---|---|
Save from a workflow |
Convert a code node, such as SQL or Python, into an operator and specify its directory and database |
Write directly in Catalog |
Create an operator in a database and maintain its metadata |
Common custom-operator metadata includes identifier (English), language (Python / SQL / Go, and others), description, parameter signature (name / type / required / default), and version history. A custom operator can be published as an API or used as an agent tool (see Guide · Catalog / Data Processing for instructions).