Routines
Work that starts without you
A routine runs on a schedule, or from something happening in an app you have connected. There are 13 event triggers today, and results are delivered to Slack or email rather than waiting in a dashboard.
The problem
The work that comes back every week
Check the inbox, triage the form, review the pipeline, chase the thread, write the update. None of it is hard. All of it is recurring, and all of it degrades quietly when the week gets busy.
What it does
Trigger on a clock
Daily at a time, or on an interval, optionally limited to working hours or particular days.
Trigger on an event
A message in a channel, a pull request opened, a Notion page created, a file added to Drive, a calendar event, an email arriving.
Delivered where you already are
The result posts to Slack or email. You find out because it told you, not because you remembered to look.
Unattended work is held to stricter limits
A routine runs when nobody is watching, so it is deliberately allowed less than a person is.
- A routine can never reach shell execution, on any plan, with any setting
- Write access for scheduled work is a separate opt-in from write access in chat
- A burst of matching events collapses into one run rather than firing repeatedly
- The trigger catalog deliberately excludes anything Indexbrain does not actually ingest, because a trigger that can never fire is worse than a missing one
The rest of it
Give your AI a company to work for
Connect your tools, and every agent you already use starts the day knowing how your company actually works.