Jobs
A job is a small routine: collect → write → deliver, on a schedule or just once. It is always personal: it reads with your permissions and delivers only to you.
The steps
| Group | Steps |
|---|---|
| Collect | Search memory, Task list, Task statistics, Weather |
| Process | Write with AI |
| Logic | If, If something was found |
| Act | Create task, Project from template, Email me, Notify me |
You build it from the Jobs page (New job) by linking steps; each step declares what it produces and the next one can use it. The history of every run, step by step, is on the job's page.
Examples
- Every Monday at 9: Task statistics for project ABC → Notify me with open, closed and overdue.
- Every day: Task list of tasks coming due → Write with AI a summary → Email me.
- Every two weeks: Project from template "Sprint {date}" from the Sprint template, with the people chosen once.
The plan count
Every step that does something counts as one automation step; logic steps are free. The plan gives each person a number of steps per month (they are not pooled between colleagues; the count restarts on the first of the month). The Jobs page shows how many you have used. The Write with AI step also uses AI credits.
Jobs shared in a project
A project's Manager can publish one of their jobs as a project template: every member finds it under Project templates and activates their own copy, which runs with their permissions and counts their steps. Republishing updates the template, not the copies.
There are no organization jobs
A weekly team summary is a job that each person has: everyone receives only what they can see.
Drafts from chat
Ask the assistant "every Friday, send me the overdue tasks in project ABC": it prepares the job draft, you open it in the editor and save it yourself.