Set up repeatable work.
For a job you repeat, build a workflow: a set of steps your agents follow the same way every time. You choose the checks, and you choose which steps wait for your OK.
Build it on the canvas
Open Workflows and create one. The canvas starts with Start fields, the details each run needs from you, such as an amount or a date. They’re optional. Then choose who does the first step and write what they should do, the way you’d brief a person.
Under a step, click + and choose what happens next:
- Add a step hands the work to another agent.
- Check something sends the work down different paths, depending on a result.
- Continue with an existing step joins this path back into another one. Steps that would create a loop aren’t offered.
Use Undo and Redo while you work. If something’s missing, the step says so in plain words, such as “Add an instruction”. Build and edit on a computer. On a smaller screen the canvas is view-only.
Pass results along
Under Results to pass on, list what a step hands to the steps after it. Each result has a type: Text, Number, Yes or no, or Pick from a list. Later steps can use earlier results in their instructions.
Add checks
A check reads like a sentence: “If Amount is more than 500, then Step 2.” You can compare a result using is, is not, is more than, is at least, is less than, is at most, is one of, or has a value. Kautuka tries the checks in order and follows the first one that’s true. If none are true, it takes the Otherwise path. The rule decides the path, not the agent.
Choose where you sign off
Reviews are set step by step. Tick Check with me first on the steps you want to see, and the canvas marks them Waits for your OK. Steps without it pass their results straight on.
When a marked step finishes, the run waits for you. The review appears on the run’s page, on the Approvals page, and on Telegram or Slack if you’ve connected a channel. Reviews can have a Telegram bot of their own if you’d rather keep them apart from chat. You can:
- Approve: the step’s results are passed on and the run continues.
- Request changes: say what should change, and the step runs again. You can ask twice for each step; after that, approve or stop.
- Stop run: the run ends there.
Until you approve, that step’s results aren’t passed on. A review doesn’t wait forever: if it runs out of time unanswered, the run stops rather than carrying on. Tools set to Ask inside any step still ask you as usual.
Test a step
Test this step runs one step with sample details you enter. It stops before the agent uses any tool, and it doesn’t create a run. Save the workflow before you test.
Run it, or put it on a schedule
Select Run workflow and fill in the start fields. To run it regularly, select Autopilot on the workflow’s page and set the start values once; see Schedules. Each run has its own page, with the path it took marked on the picture and a Step journal of what each step did and passed on.
Restarts
If Kautuka restarts, runs that were working pick up again, and a run waiting for your review keeps waiting. If a run stopped part-way through changing something in another service, check that service before you try again.
Archive or delete
A workflow with past runs can be archived. It won’t run any more, but its runs stay, and you can restore it any time. A workflow that has never run can be deleted.
For individual tasks and the activity trail, see Use Kautuka. For connector, credential and shared-agent boundaries, read Security.
Technical details
Each run keeps the version of the workflow it started with, so later edits don’t change a run in progress. Checks compare a step’s typed results directly; no model is involved in choosing a path. A workflow belongs to the person who created it, and its steps can use any agent that person can use. Each step is an ordinary agent run, with the same sandbox, tool modes and run history. Restart recovery doesn’t make outside actions safe to repeat or guarantee they happen exactly once; check the run and the other service before retrying.