Workflows and apps

Routines and listeners

Flexible workers and teams that wake on a schedule, when a connected service changes, or when a webhook arrives.

Updated 30 Sept 2026

A routine is a worker that wakes itself

A flexible worker or team starts on a timetable when you add a time in its When it runs screen, or when a new flexible worker's When to work is On a schedule. Open When it runs from the worker's Settings tab, or with the When it runs clock button at the top of a flexible worker or a team room. Add a time asks for the schedule, a name and what it should do, and each run shows on the worker's Runs tab.

A new time: the schedule, the next three runs, a name and what it should do.
Try this
✦When it runs → Add a time. Name: Monday scan. What should it do? Check the top three competitors' prices and new releases and report what changed, with links. Repeats: Every week, Monday, 08:00.
What you getNext three runs shows the coming Mondays before you save; the time appears under Times and the first report arrives Monday morning.

Choose the schedule

Quick picks such as Hourly, Weekdays 9:00 or Daily 8:00 set a time in one click. Custom's Repeats offers Every hour, Every few minutes, Every day, Weekdays, Every week and Every month, and Advanced takes a cron line, each in the time zone you pick. Add another time puts up to eight times in one set, and any matching time starts a run. Next three runs shows before you save, so a wrong time zone or day shows up early.

Every day at 7:30, with the next three runs previewed before saving.
Try this
✦Repeats: Every day at 07:30. Then Add another time: Fridays 16:00.
What you getNext three runs lists the coming runs across both times, and they share one row under Times.

Listeners: react to a connected service or a webhook

Under When something happens in When it runs, pick a connected service such as Slack or Gmail, then the Account and the Event, for example Bot is mentioned or New message. Webhook gives the worker its own address; anything posted there wakes it with the payload. Each listener row reads Listening, with a switch to pause it, Test and Remove.

A listener: pick the connected service, the account and the event.
Try this
✦When something happens → Slack. Name: Mentions in #launch. What should it do when this happens? When the bot is mentioned in Slack, answer from the launch plan in the workspace and post a one-line reply. Event: Bot is mentioned.
What you getThe listener row appears; the next @mention in Slack starts a run you can open from the Runs tab.

Run now, pause, and the run history

Each set of times in When it runs has a switch, Run now, Edit, History and Remove. Run now starts a run immediately without touching the timetable; a set you switch off keeps its times but skips them until you switch it back on. History lists past runs, and every run also shows on the worker's Runs tab with its own transcript and files.

Editing a set of times: its switch, Run now, Edit, History and Remove.
Try this
✦In When it runs, click Run now on Monday scan, then open the new run on the Runs tab.
What you getA fresh report with links, and the Monday timetable unchanged.
GUIDED LEARNING

Practise this in Oppermind Academy

Follow the related tutorial or course and apply the concept to a real task.

Open learning path