Create a workflow
At a glance
Build a visual workflow by assembling trigger and action blocks on a canvas.
Before you start
- You have access to a Ontologie workspace.
- You have identified the process to automate (for example: enriching entities, sending notifications, transforming data).
Steps
1. Open the canvas
Open Workflow Builder from the sidebar. Select an existing workflow or click New workflow to create one.
Screenshot coming soon: Workflow Builder canvas selector.
2. Discover the canvas
The canvas opens with a pre-placed Start block. This is the entry point of your workflow: every execution begins with this block.
Screenshot coming soon: canvas with pre-placed Start block.
3. Add blocks
Click the + button or drag a block from the side panel to add it to the canvas. Blocks are organized by category:
| Category | Blocks | Usage |
|---|---|---|
| Trigger | Start, Schedule, Webhook, Entity trigger | Workflow entry point |
| Flow | Condition, Loop, Split, Merge | Branching logic |
| AI | Prompt, Semantic search | Query an LLM or the knowledge base |
| Data | Ontology, Entity lookup, Transform, Filter | Read and transform data |
| Integration | Tool, Subflow | Call an external service or a sub-workflow |
4. Connect the blocks
Connect blocks by dragging a link from a block's output (bottom point) to the next block's input (top point). The connection order defines the execution path.
5. Configure each block
Click a block to open its settings panel. Each block type has its own options: prompt text, target entity, branching condition, etc.
Screenshot coming soon: block configuration panel.
Example: for a Prompt block, enter the question text and select the AI model to use. For a Condition block, define the logical expression that determines which path to follow.
6. Save the workflow
Save your workflow with the Save button. Your changes are preserved and the workflow is ready for testing.
Start with a simple workflow (Start, a single action block, Output) to validate the concept. Add steps and branches progressively.
Expected outcome
Your workflow is saved and visible in the list. The blocks are connected and configured, and the workflow is ready for a test run.
Limits and common issues
- An unconnected block will be ignored during execution.
- Make sure every branch (after a Condition or Split block) ends with a terminal block or rejoins the main flow.
- There is no limit on the number of blocks per workflow, but a simpler workflow is easier to debug.
Next steps
- Run and debug: launch a test and analyze the results.
Need help?
Write to us: Support and contact.