What routines are
Scheduled work with a human owner, a delivery destination and explicit sharing.
Work on a schedule
A routine runs a described job at a scheduled time and delivers the result to a channel or DM. You can create one directly or turn a useful one-off job into recurring work.
Examples:
- Monday pipeline review with links to deals that need attention.
- A weekday report of unresolved support issues.
- A monthly comparison of signups and activation.
Each run uses workspace credits. Its cost depends on the work it does; see How credits work.
What belongs in a routine
Specify the sources, time window, output, schedule and destination. “Report last week's signups every Monday at 09:00 Europe/London in #growth” is easier to verify than “keep an eye on growth”.
A routine can include instructions, skills and files that should be available each time. Run it once and check the result before relying on the schedule.
Ownership and sharing
A routine runs with its owner's authorised integration access. Read and Edit permissions control who can inspect or change its definition. Posting results to a channel does not give everyone there ownership.
A routine created in a channel initially gives that channel Read access. One created in a DM starts private, even if it delivers results to a channel.
Approvals during a run
Slack reports post automatically. Actions such as sending email, placing a phone call or inviting calendar attendees can be held for the owner to handle interactively. The routine continues with work it can finish and reports what it held.
Start with Creating a routine, then use Managing routines for permissions, changes and recovery.