Routines
Every employee has Routines, and they hold two kinds of work: what runs on the clock, and what starts on an event. This page is the first kind — see Triggers for the second.
A superpower is the third way work starts: you launch it yourself from a form. Reach for a scheduled routine when the same instruction should repeat, and an event routine when another system decides the moment.
A routine's kind is settled when you create it. Nothing converts a scheduled routine into an event one, or back — they are stored apart. If you need the other kind, create the other kind.
Scheduled — on a clock
A scheduled routine is a standing instruction assigned to one employee: an instruction, a cadence, a destination for the result, and a choice between continuing the last conversation or starting fresh. To create one, follow Put work on a schedule.
Examples
Run, pause, history
Every routine can be run on demand, paused, and inspected — each run keeps its output and its log.
The library
Ready-made routines per role, installed onto an employee with a cadence you can then edit. An installed one carries the catalogue entry it came from, and you can rename it afterwards.
Event — when something happens
The other half of Routines: a URL another system hits to start real work. A lead lands in your form, the webhook fires, the employee qualifies it and drafts the reply.
See Triggers for the setup, the payload templates, the limits and the history.
Where the work shows up
Both kinds create a task you can follow in the Inbox — with its runs, the employee's comments, and any approval it is waiting on. See Autopilot & Goals.