Anatomy of a workflow
Every workflow needs a trigger. The trigger kind decides when it runs:
- Manual run - only when someone presses Test run.
- Schedule - a cron expression with a timezone.
- Alert fires - bound to one of your alert rules.
- Webhook - an external system calls in.
How a run executes
Ankra walks the graph node by node. An agent step opens an agentic session with the step’s goal prompt and waits for it to finish; a condition picks the branch whose comparison matches; an output posts its notification and completes the run. Recent runs are listed per workflow in the Inspector. When a run reaches an Approval node, it pauses and files a ticket on the AI Board directly into Awaiting approval. Approving - from the Inbox or the ticket - resumes the run; denying cancels it. The run’s outcome settles the ticket when it finishes.Approval gates are how an automation stays safe on a schedule: the workflow can investigate and prepare autonomously overnight, but nothing irreversible happens until a person signs off.
Templates
Start from a template in the Workflows list seeds a ready-made graph you can adapt:- Nightly cluster fix plans - scheduled sweep that drafts fixes and parks them for approval.
- Daily insight digest - collects the day’s findings into one notification.
- On alert: diagnose - triggered by an alert rule, investigates, and reports.