Compiled by an agent, never configured by you
There is no builder to learn, no node palette, no expression language. Describe the rule the way you would say it out loud. Your AI project manager compiles it into a plan that has been checked against the tools it is allowed to use, tells you what it will cost to run, and the card you approve becomes the automation.
“When a support ticket is marked urgent, post it in the on-call room, assign it to whoever is on duty, and remind me in two hours if it is still open.”
Your sentence is kept. The machine code is generated.
Every automation holds three things, and you only ever read the first one again.
What you said
Your own sentence, stored as the source. When you want a change, it is edited and recompiled — you never patch generated machinery by hand.
The checked plan
Ordered steps, each naming a real tool with real arguments, validated against what the agent is permitted to do in that room before you ever see it.
The instructions to run it
For the steps that need judgement, the compiler writes the brief the agent will work from — approved on the same card, not hidden in a prompt somewhere.
Four moments, and only one of them is yours
Describe the rule
In the command bar of any agentic room, in the words you would use with a colleague. One sentence is usually enough.
Read the card
The trigger, every step, the tools each one uses, what it will cost per firing and roughly how often it will fire.
Approve it
The card is the artifact. Approving it puts the automation live; nothing runs on a plan you have not seen.
Watch the history
Every firing is recorded with what it did and what it created. Pause it, revise it in a sentence, or roll back to an earlier version.
Six ways an automation starts
Anything that happens inside an agentic room can start one — including things people do without thinking of them as events.
A row is created
By a person, a form, an import or the agent — anything that lands in a table.
A row enters a state
Not every save: the moment a row first matches the conditions, and not again until it stops.
A form is submitted
Public forms, internal forms, and forms bound to a step of a running process.
Something is said
A message posted in a room, a decision recorded in minutes, a mention of a person.
Work changes hands
A task completed, an approval decided, a file uploaded, a meeting ended.
A time comes round
Every weekday at nine, the first of the month, two hours after something happened.
Most automations cost nothing to run
The compiler decides which of two runners an automation needs, and the answer is on the card before you approve it.
Every step is a known action
Zero agent credits, every firing
When the plan is entirely made of things the system can simply do — create the task, post the message, set the reminder, update the row — no model is involved at run time at all. The plan is walked directly.
- Runs in milliseconds
- Identical every time
- Free to fire as often as it needs to
A step needs judgement
One agent run per firing
Summarise the thread, decide the severity, draft the reply in the customer's language. The agent runs the plan it was given — and the plan is a contract: it may skip a step, but it cannot invent one.
- Bounded by the tools the plan declares
- Capped per day so a loop cannot run away
- Recorded run by run, with what it produced
Autonomy with a paper trail
An automation acts on behalf of a named person, inside one room, using a credential that works nowhere else.
Acts as somebody
Every automation runs under its owner. It can never reach data that person could not reach, and the audit trail names them.
The plan is a contract
Permitted tools are derived from the approved plan, not from the instructions — so a reworded brief cannot widen what it may do.
Full firing history
Every run, what triggered it, what it created, and whether it succeeded — kept for review long after the fact.
Approval before action
In rooms set to ask first, anything an automation would write comes back as a card for a person to approve.
A forecast before you commit
The card estimates how often it will fire, so a rule on a busy table is a decision rather than a surprise.
Versions and a pause button
Revise in a sentence and keep the old version; pause an automation without deleting the work it has already done.
An automation is a one-step process. A workflow is the rest of them.
One rule inside one room is an automation. The moment a process needs a person to approve, a second department to act, a deadline, or a way back to whoever asked — it is a workflow, and the same compiler builds it.
When a draft is ready, tell the editor.
Draft → editor review → legal sign-off → publish → tell the requester.
What teams actually automate first
Nobody has to remember to chase
When a task passes its due date and is still open, tell the owner and their manager — once, not every hour.
The customer hears back the same day
When a public form is submitted, acknowledge it by email and open a row for whoever picks it up.
Meetings leave work behind
When minutes are published, create the action items, assign them, and put them on the board.
The board matches reality
When a deal reaches negotiation, create the checklist, notify the sales head and set the follow-up.
Monday morning writes itself
Every Monday at nine, post the week ahead in the room: what is due, what is late, what is waiting on whom.
Escalation is not a favour
When a ticket marked critical has had no response in two hours, tell the on-call engineer and the support head.
Say the rule out loud. Approve the plan.
The chasing, the copying, the reminding and the telling-people — the work that fills a day without filling a plan. Describe one of them and see it come back as something you can approve in a minute. Build it free on any plan, and go live with AI Office Pro.
Explore the rest of the platform
Every part of Qik Office shares the same rooms, the same people and the same permissions — so the work one part produces is immediately usable by the next.