Built-in operators
Built-in operators are platform-maintained capabilities executed by GeniSpace Worker. They appear in the catalog when enabled for the environment and Space. The live catalog, not a static list in this guide, is the source of truth.
Find an operator
Open Console → Operators or the WorkflowStudio node library. Search by name, description, category, or tag. Inspect:
- available methods;
- input and output Schema;
- required connections or permissions;
- configuration fields and Secret handling;
- active status and supported use cases.
Dataset and Datasource capabilities may appear in their own node-library categories even when execution is operator-backed.
Enable and configure
- Select the operator in the catalog.
- Review all methods and data access requirements.
- Configure user-controlled values and required connections.
- Store sensitive values as Secrets.
- Enable the operator for the intended Space or environment.
- Test a method with non-production input.
- Add it to a workflow or an authorized agent tool catalog.
System-owned implementation configuration is managed by platform administrators. Space users configure only the fields exposed by the product.
Common categories
Depending on deployment, the catalog can include:
- Dataset query, count, vector search, and full-text search;
- data transformation and general utilities;
- REST and HTTP requests;
- document, text, image, audio, or media processing;
- database Schema inspection and SQL generation utilities;
- messaging, email, or supported publishing integrations;
- platform data and application operations.
An operator being listed does not guarantee the current user can execute it. Authorization is evaluated for the operator and each referenced resource.
Use in a workflow
Add the operator node, choose a method, map typed inputs, configure timeout/error handling, and connect structured output downstream. Run the workflow with normal, empty, and invalid input before enabling its trigger.
Inspect the node result rather than relying only on a success label. A successful call may still return zero records or a business-level rejection.
Use as an agent tool
Only selected operators are exposed to an agent. The runtime considers the agent form, Ask/Agent mode, Space permissions, application-local tools, and tool configuration.
Good tool-facing methods have:
- a unique, action-oriented name;
- a description of the correct selection conditions;
- minimal typed arguments;
- structured result and explicit empty state;
- safe error information;
- confirmation for destructive actions.
Dataset tools must preserve the distinction between exact query/count, full-text search, and vector semantic search. Top-K vector results still require qualification against returned evidence.
Updates
Platform updates can fix or extend a built-in operator. Before changing an exposed contract, administrators should identify active workflow and agent consumers and run regression tests. Users should not edit platform-owned runtime code or system credentials.
Troubleshooting
| Symptom | Check |
|---|---|
| Operator missing | Environment availability, active status, Space access |
| Method missing | Selected operator version and method catalog |
| Validation failure | Required fields, Schema type, array/object shape |
| Unauthorized | User role, operator access, connection and target resource |
| Timeout | Remote dependency, operator timeout, parent task timeout |
| Agent chooses wrong tool | Tool description, overlapping names, input contract |
| Empty Dataset result | Search type, vectorization status, fields, filter, source records |