Documentation / Routines

Give repeatable work a rhythm.

A routine is an instruction that runs on a schedule or supported trigger. Start small, test it, and make its review point explicit.

A little help. A whole lot of possibility.
01

Define the instruction

Specify the input, expected output, limits, and what requires your approval. For example: prepare a weekday inbox summary, with suggested replies but no sending.

02

Choose a trigger

Schedules support recurring intervals and timezone-aware timing. Change watchers, webhooks, Git events, email, and Slack triggers depend on configuration. A change watcher cannot be combined with a schedule.

03

Test before repeating

Run the saved routine manually, review the result, and adjust the instructions. Use the Active setting to pause it without deleting it, and inspect run history.

04

Keep approvals in the loop

Outside-triggered work follows stricter rules. A schedule is not blanket permission for risky actions. Changes to a routine can pause previously granted scoped allowances.

One good place to start

What could your first bee help with?

Choose a role. Give it a clear job. Build from there.

A little planning. A lot of possibility.

Build your bee team.

Choose the roles you need and give your future hive a first task.

Your teammates

Planning preview · Your brief stays on your device. No account is created and nothing is submitted.