Actions
An action is a standing instruction you give Aktis: a question or task worth repeating, that runs on its own and brings the answer back to you.
:::info What this covers Actions run on a schedule. Watching a metric and waiting for it to move is a natural extension and is not built — see what an action cannot do yet. :::
The problem it solves
Aktis can already answer anything about what your customers have told you. But you have to be there, and you have to think to ask.
The questions that matter most are rarely one-offs — what are enterprise accounts complaining about this month? did the fix we shipped stop that bug showing up in support? which themes are growing fastest? Each is worth asking every week. None of them get asked, because asking is something a person has to remember to do, and the feedback keeps arriving whether anyone is looking or not.
Actions close that gap. You ask once, and Aktis keeps asking.
What an action is made of
Four things, and the last two are what make it a delegation rather than a one-off question:
| Part | What it is |
|---|---|
| Instruction | What you would have typed into Aktis. Plain language, not a query builder. |
| Trigger | When it runs: daily, weekly, monthly, or at the end of a cycle. |
| Output | What it produces: a report, an alert, or a strategic artifact. |
| Delivery | Who gets told, and where. |
The anatomy of an action covers each in detail, including what is available today.
What that looks like in practice
"Every Monday, summarise what enterprise customers said last week and flag anything that contradicts the current roadmap."
"Every morning, tell me what feedback came in overnight and whether anything in it looks urgent."
"At the end of each cycle, draft a report on which shipped projects actually changed the feedback we're getting."
"Every Friday, list the themes that grew fastest this week and how many customers each one came from."
The first is a report you read on Monday. The second is a daily heads-up. The third is an artifact filed at the end of a cycle. The fourth is a weekly pulse.
All four are the same object — an instruction, a trigger, and somewhere to put the result.
Why this belongs to Aktis
An action is not a separate automation engine bolted on beside the assistant. It is the same assistant, given a standing instruction instead of a live one, and that matters for a practical reason: an action can do exactly what you can already get Aktis to do in chat.
There is no second, weaker query language to learn, and no gap between the things you can ask and the things you can automate. If Aktis can answer it once, you can have it answered every week.
It also means an action inherits the same discipline about evidence. A weekly summary is grounded in the feedback and documents your organization has actually ingested, and it says when the evidence is thin — exactly as an answer in chat does. An automated report nobody can trace back to a source is one nobody trusts by the third week.
What an action is not
- Not a rules engine. You describe an outcome in your own words. There is no trigger-condition-branch tree to build.
- Not a notification setting. A notification tells you something happened. An action does the thinking, tells you what it means, and leaves something you can read afterwards.
- Not autonomous change. An action drafts and reports. Whether anything is accepted, published or pushed to a delivery tool stays a human decision. The value is in the noticing, and noticing is safe to automate in a way that acting is not.
Who can create one
Any member of your organization can create, pause and delete actions. An action reads what the organization has already ingested — it reaches nothing a member could not ask Aktis directly.
Two things are worth knowing before you write a lot of them:
- Every run costs a model call. A daily action is thirty runs a month. Start with the questions you would genuinely have asked by hand.
- Actions are shared. They belong to the organization, not to the person who wrote them, so a colleague can see, pause and run yours — and yours keep running after you move to another team.
Questions about actions: [email protected]