Workflow settings
Budget, limits and allowed nodes for all workflows; cost per run and per node.
Owners and admins decide under Administration → Workflows how much your workflows may cost, how often they run and which nodes are allowed. The page also shows what each workflow has cost so far.
What a workflow costs
Costs only arise from AI calls to external models and from images. Your own models operated by Kasimir are free. Every AI call is booked with the tokens used and the model's price; an image has a fixed price.
Where you see the costs:
Runs of a workflow: the Cost column per run.
A single run: Cost of this run and Cost per node. Hover over a node to see model and tokens.
Administration → Workflows: this month's AI costs for the whole workspace and per workflow (month and total).
Cost per node is available for runs from 3 October 2026 on. Older runs only show the total.
Cost & limits
All amounts in euros, per calendar month. Leave a field empty for no limit.
Setting | Effect |
|---|---|
Workflow budget per month | Cap on the AI costs of all workflows together. Owners and admins get an inbox message and an email at 50, 90 and 100 %. From 100 % no new runs start. |
Default monthly limit per workflow | Applies to every workflow without its own monthly limit. |
Highest monthly limit per workflow | Caps what can be entered on a single workflow; the default may not exceed it. On its own it is not a limit. |
Default limit per run | Stops a single run as soon as its AI costs reach the limit. |
Runs per hour at most | Default for all workflows. Protects against a flood of triggers, such as a webhook firing in a loop. |
A workflow budget of €0 counts as an empty field. A monthly limit of €0, in contrast, blocks the workflow, and a run limit of €0 allows no AI call – just like the personal limits under Budget & Usage.
Limits on a single workflow
In the workflow editor under Settings → Cost & limits a workflow gets its own values: Monthly limit, Limit per run and Runs per hour at most. Empty fields use the workspace default. Anyone who may edit the workflow can change them; the monthly limit may not exceed the workspace's highest monthly limit.
When a workflow reaches 80, 95 and 100 % of its monthly limit, the person who created it gets an inbox message and an email.
What happens when a limit is reached
Limit | Result |
|---|---|
Workflow budget used up | New runs of all workflows are refused: manual starts, webhooks and forms get an error message, schedules skip their slot, integration triggers skip the event. AI calls in runs already in progress fail. |
Monthly limit of a workflow reached | The same, for this workflow only. |
Limit per run reached | The run's next AI call is refused; the run fails at that node. |
Runs per hour reached | Further starts are refused until the hour is over. Schedules skip the slot. |
The check happens before every AI call. The call that crosses a limit still completes – costs can therefore exceed a limit by one call.
Kasimir checks for notifications about every ten minutes. Each threshold is reported only once per month.
At the start of the month counting starts again at zero; blocked workflows run again.
The workflow budget only counts the AI costs of workflow runs. It applies in addition to the settings under Budget & Usage.
Nodes & triggers
Switch | When off |
|---|---|
Code node | The editor no longer offers the node, and workflows with a code node cannot be published. Existing workflows fail at the code node – in real runs and in test runs. The node shows a notice in the editor. |
HTTP node | The same for outgoing calls to external addresses. |
Public forms | Form links respond as if the form did not exist, and workflows with a form trigger cannot be published. Switched back on, existing forms are reachable again immediately. |
All three are on by default. Webhooks are always secured (secret or signature) – there is no switch for that.
Manage workflows
The table at the bottom of the page lists all workflows of the workspace, including private ones: name, owner, status (Published or Draft), visibility, total runs, costs this month and in total, the effective monthly limit, last run and last change. The search field finds workflows by name or owner. Clicking a row opens the editor, clicking the number of runs opens their list.
Access
Only owners and admins see this page. Who may create, share and start workflows is set under Administration → Roles and permissions. More on building workflows: Workflows.