Skip to content
Routines and workflows

It keeps working after you have gone home

A routine wakes an agent on a schedule, a webhook, or a message in a channel. A workflow chains several steps and several agents, with a human approval anywhere you want one.

  • Schedule, webhook, or a message starts it
  • Each step can use the result of the one before it
  • Every run is kept, with what each step did
Morning digestRun now
Every weekday, 9:00trigger
+
Atlas writes the digestwhat changed since yesterday
+
Ask a personsend it?
Ran in 6 s, digest posted to #ops

How it works

  1. 1

    Pick what starts it

    A time of day, an incoming webhook, or someone writing in a channel. You can require a word, so only messages that mention it fire the workflow.

  2. 2

    Lay out the steps

    An agent task, a question for a person, a wait, a post to a channel, a call to your own endpoint. Steps hand their output to the next one.

  3. 3

    Watch it run

    Press Run now and follow it live. Every past run keeps what each step received and returned, so a failure is something you can read, not guess at.

Questions about this

What happens if a step fails?

The run stops at that step and says why. Nothing after it runs. Fix the step and start the run again.

Can a workflow start itself in a loop?

No. Only messages from people start a channel-triggered workflow, so a workflow that posts into the same channel cannot wake itself.

Do routines cost tokens when nothing happens?

A routine that wakes an agent costs what that agent reads and writes. A workflow step that posts a fixed message costs nothing.