Workflow building blocks
All building blocks of the workflow editor: what they are for and what to keep in mind when setting them up.
A workflow consists of building blocks that you connect on the canvas. This page describes each block: what it is for and what to keep in mind when setting it up. How to create, run and share a workflow is described under Workflows.
Passing values on
Every block can use results of earlier steps. You insert them with double curly braces; the variable picker in the editor helps you with this.
Syntax | Meaning |
|---|---|
{{trigger.input.feld}} | Value from the start form, e.g. |
{{schritt.output}} | Result of an earlier step |
{{schritt.output.feld}} | A field of a structured result |
{{schleife.output.item}} | The current item in a loop ( |
{{frage.input.antwort}} | The answer from “Ask user” |
The name before the dot – the technical slug – appears in the block’s header as long as no display name is set; otherwise in the settings panel (the Slug field, or as the placeholder of the Name field). You change it via rename in the ⋯ menu.
Trigger
Every workflow starts with exactly one trigger: manually via the start form, on a schedule, via a public form, via webhook or through an event in an integration. Details under Workflows.
AI
Building block | What for | Good to know |
|---|---|---|
AI step | Gives a language model a task – with instructions, knowledge and optionally tools (web search, reading pages, document search). | Optional structured output with fixed fields. In the agent field (“Assistent”), an agent can provide role, model and tools; in manual runs the person starting the run must be allowed to use it, automatic runs (schedule, form, webhook, integration) only allow company-wide agents without a project. |
Check | Checks a text for inappropriate content, personal data or manipulation attempts. | Result: passed yes/no with a reason – works well with a branch. |
Image generation | Creates an image from a description. | Only if your company allows the image generator. |
Logic
Building block | What for | Good to know |
|---|---|---|
Branch | Splits the flow into “yes” and “no” based on one or more conditions. | Conditions can be combined with “all” or “any”. Not inside a loop. |
Router | Several named routes; every matching route runs. | A route without a condition always runs, the “otherwise” route only if no other matches. Not inside a loop. |
Loop + Aggregate | Repeats the steps in between for each item of a list and combines the results. | Without its own cap at most 200 items – a longer list stops with a message. With “Max. Iterationen” (max. iterations) up to 1,000; the rest is skipped. Loops cannot be nested. In the run view, the first 100 iterations of each step can be inspected one by one. |
Code | Runs your own Python code, e.g. for calculations or transformations. | No internet access, at most 30 seconds. Your company can switch this block off. |
Pause
Building block | What for | Good to know |
|---|---|---|
Ask user | Pauses and asks for input; then continues. | The answer is then available as a value. Not inside a loop. |
Delay | Waits for a set time. | Not inside a loop. |
Data
Building block | What for | Good to know |
|---|---|---|
Table | Reads rows from an Excel or CSV file. | Ideal as the list for a loop. |
Document search | Searches your knowledge for matching passages. | Can be limited to specific sources; only what the person starting the run may see is searched. |
Web search | Searches the internet. | Your company’s source policy applies here too. |
List files | Lists the files of a cloud folder. | For every connected provider. |
Read file | Fetches a file and reads its text. | Works well with “List files” and a loop. |
Output
Building block | What for | Good to know |
|---|---|---|
Document | Creates a Word, Excel, PowerPoint or PDF file – from text or your own template. | The file appears in the run result for download. |
Save to storage | Stores a result permanently as a file. | |
Output | Names a value as a result of the workflow. | Appears on the result page. |
Upload file | Writes a file to a cloud folder. | For every connected provider. |
Fill form | Fills an existing PDF form – with fixed values and details found by the AI. | Every AI value needs evidence from the text; a person reviews the draft before the final version. PDFs without form fields get their fields once in the editor. |
Actions
Building block | What for | Good to know |
|---|---|---|
Send email | Sends an email. | If the recipient comes from AI or file values, the run pauses or stops – so no email reaches the wrong recipient. |
Post message | Posts a message to a channel, e.g. in Microsoft Teams. | |
Send notification | Puts a message in the inbox in Kasimir. | Goes to the person who started the run. Runs without a starting person (schedule, webhook, form, integration) create nothing; in a dry run the message is only described. |
HTTP request | Calls an external interface. | Public https addresses only. Not inside a loop. Your company can switch this block off. |
Integrations
Connected services have their own blocks: Outlook (create draft, send email, create event), Teams (send card), OneDrive and Google Drive (upload file), Google Calendar (create event), Google Sheets (append row) and MSO (read, create, update data). They are available once the integration is connected – see Integrations.
Run status
Status | Meaning |
|---|---|
Queued / Running | The run has been accepted or is being executed. |
Completed | All steps are done. |
Failed / Cancelled | A step failed or someone stopped the run. |
Waiting for input | An “Ask user” step or a review is waiting for you. |
Waiting | A delay is running, an approval is pending or a selected source is still being read in. |