Workflow Builder — Interface
Table of contents:
The workflow builder is a visual editor where you build automation step by step — without writing any code. Each element is arranged in a logical sequence visible on screen as a flowchart.
Interface overview
The editor consists of three main areas:
┌─────────────────────────────────────────────────────────────────────┐
│ TOOLBAR (top bar) │
│ Add block │ Run workflow │ Execution history │ Logs │ Variables │
├──────────────────┬──────────────────────┬───────────────────────────┤
│ │ │ │
│ TOOLS PANEL │ CANVAS │ PROPERTIES PANEL │
│ │ (workspace area) │ │
│ Available block │ │ (appears after │
│ types: │ [block 1] │ clicking a block) │
│ │ ↓ │ │
│ • Trigger │ [block 2] │ │
│ • Get data │ ↓ │ │
│ • Flow control │ [block 3] │ │
│ • Action │ │ │
│ • AI Agent │ │ │
│ │ │ │
└──────────────────┴──────────────────────┴───────────────────────────┘Tools panel (left panel) — a list of available block types divided into groups. You can hide and reveal it using the "Show tools" / "Hide tools" button in the toolbar:
| Group | Contents |
|---|---|
| Trigger | Schedule, Webhook, AI Task |
| Get data | Fetching data from Google Ads, GA4, Microsoft Ads, and more |
| Flow control | If/Else, Router, Filter, Iterator (loops) |
| Action | Create task, Send HTTP, Add comment |
| AI Agent | Node with a language model (LLM) |
Canvas (center area) — this is where you arrange and visualize the workflow. Blocks appear as tiles connected by arrows. You can drag, delete, and reorder them. The "Arrange blocks" button in the toolbar automatically organizes the layout, and "Center view" resets the view to the center of the canvas.
Properties panel (right panel) — opens automatically when you click any block. Displays the configuration form for that specific block: parameters, values, and conditions.
📸 [SCREEN: full view of the workflow editor — tools panel on the left, canvas in the center with a visible block sequence, properties panel on the right with an open form for the selected block]
Adding and connecting blocks
Adding a new block:
- In the tools panel on the left, find the block type you want to add (e.g., "Create task" from the Action group).
- Click the "Add block" icon in the toolbar or click the
+icon directly on the canvas — a selection window will open with a list of available blocks. - Select a block from the list — it will appear on the canvas ready for configuration.
Configuring a block:
After adding a block, click it to open the properties panel on the right. Each block type has its own form:
- Schedule Trigger — select frequency, time, time zone, start date, and end date.
- Get data — select the source (e.g., Google Ads), account, and metrics to fetch.
- Flow control If — define a condition (e.g., "CPC > 5") and paths for "yes" and "no".
- Action Create task — fill in the title, description, assignee, and due date.
Connecting blocks:
Blocks are connected automatically in the order they were added. For blocks with branching (If, Router), each branch is a separate path with its own blocks.
The trigger must always be the first block in a workflow — you cannot add a Trigger block in the middle of a sequence. The system will block such an attempt.
Deleting a block:
Right-click the block or use the "Delete block" icon in the toolbar. Blocks after the deleted one will automatically be connected to the preceding ones.
📸 [SCREEN: canvas with the block selection window open (+ button) and the properties panel for a Flow control — If block on the right]
Test mode vs. production mode
Before enabling a workflow permanently, you can run it once and observe the execution in real time.
Test run:
- In the toolbar, click the "Run once" button.
- The Inspector panel will open on the right with a live execution preview.
- The system runs the workflow once and shows the result of each block step by step.
- Each block is color-coded:
- Green — block executed successfully
- Red — block encountered an error (clicking shows details)
- Gray — block has not yet been executed or was skipped by a Flow control condition
📸 [SCREEN: Inspector on the right side during execution — list of blocks with color indicators and a preview of input/output data for each block]
Production mode:
Once the workflow is working correctly, activate it from the workflow list. Click the action menu (three dots) next to the given workflow and select "Activate". From that point on, Sembot runs it automatically according to the trigger.
To stop the workflow, select "Deactivate" from the same menu.
| Test run | Production mode | |
|---|---|---|
| When does it run? | On demand (once, manually) | Automatically based on the trigger |
| Results visible? | Yes, in the Inspector in real time | In execution history |
| Impact on data? | Yes — actions execute for real | Yes |
| Purpose? | Verification before deployment | Normal system operation |
Important: A test run executes the workflow for real — if the action is "Create task," the task will actually be created. It is worth removing test effects before activating the workflow in production.
Workflow versioning
Sembot does not have an automatic versioning system. Every saved change overwrites the current workflow definition.
Available mechanisms to protect against losing work:
- Export workflow — in the editor menu (three-dot icon or dedicated button), select "Export workflow". Sembot will download a JSON file with the full definition. You can store it locally as a backup or reference point.
- Import workflow — if you want to restore an older version, select "Import workflow" and load a previously saved JSON file. Note: importing overwrites the current workflow definition.
- Execution history — in the toolbar, click "Execution history" to view run statistics (how many times it ran, how many successes, how many errors). This is not a history of configuration changes, but it helps you assess from when the workflow has been running correctly.
Recommendation: Before making any major changes to an important workflow — export it first. Treat the JSON file as a backup.
📸 [SCREEN: editor menu with the "Export workflow" and "Import workflow" options]