Workflows and apps

Routines and listeners

Agents that wake on a schedule, when a connected service changes, or when a webhook arrives.

A routine is an agent that wakes itself

New routine, or an agent whose When to work is On a schedule, makes an agent that starts on a timetable and lists under Routines and listeners. Each run is a normal session you can open, read and answer. The editor asks for a Name, Instructions, and When to work, then the schedule.

New routine: name, instructions, when to work, the schedule and the next three runs.
Try this
New routine. Name: Monday scan. Instructions: Check the top three competitors' prices and new releases and report what changed, with links. Frequency: Every week, Monday, 08:00.
What you getSave routine shows the next three runs before it exists; the row appears under Routines and listeners and the first report arrives Monday morning.

Choose the schedule

Frequency offers Every hour, Every day, Every week, Every month, a custom interval and an advanced cron line, each with a time in your timezone. Add up to eight timetables with + Add another schedule; any matching schedule starts a run, and overlapping times produce one run. Save routine previews the next three runs first, so a wrong timezone or day shows before it costs anything.

Every day at 7:30, with the next three runs previewed before saving.
Try this
Frequency: Every day at 07:30. Then + Add another schedule: Every week, Friday, 16:00.
What you getThe preview lists the next three runs across both timetables; they feed one routine and one row.

Listeners: react to a connected service or a webhook

When a connected service changes turns the agent into a listener: choose the Service (a connected account such as Slack or Gmail), the account, and the event, for example Bot is mentioned or New message. When a webhook arrives gives the agent its own address; anything posted there wakes it with the payload. Listeners sit under Routines and listeners with Pause listening and Resume listening on the row.

A listener: pick the connected service, the account and the event.
Try this
Name: Mentions in #launch. Instructions: When the bot is mentioned in Slack, answer from the launch plan in the workspace and post a one-line reply. When to work: When a connected service changes. Service: Slack. Event: Bot is mentioned.
What you getThe listener row appears; the next @mention in Slack starts a run you can open from the list.

Run now, pause, and the run history

Open a routine from the list to edit it. The footer adds Pause, Run now and Delete. Run now starts a run immediately without touching the timetable; a paused routine keeps its schedule but skips it until you resume. Every run is a session under Finished today with its own transcript and files, so a report from three weeks ago is one click away.

Editing a routine: Pause, Run now and Delete join the footer.
Try this
Open Monday scan, click Run now, then open the new run under Finished today.
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