Skip to main content
Routines are most useful when they are narrow, event-driven, and clear about what counts as worth notifying you. You do not need to start from a blank routine editor. After a chat handles a workflow correctly, tell the companion:
Ask it to collect the missing details before it creates the routine.

​
Start with the trigger

Choose the trigger that matches the job:
  • Daily routine for morning briefings
  • Interval routine for frequent checks
  • Cron expression for advanced schedules
  • App trigger for events such as new email
If multiple actions happen from the same trigger and share the same context, put them in one routine prompt. Good:
Less efficient:
Each routine execution runs its own AI call, so related instructions are often cheaper and easier to review in one routine.

​
Define notification rules

Tell the routine when to notify you.

​
Keep routines scoped

Avoid routines that inspect every connected app without a reason. Scope by account, folder, label, channel, project, or keyword when possible.

​
Use approval gates

For routines that can send messages or update systems, ask Strawberry to draft and notify first.

​
Review run history

Open strawberry://routines/history or a routine detail page to review run history. Use it to reduce noise, catch failures, and tune prompts. If a routine improves after tuning, ask the companion to update the routine prompt or create a skill that captures the refined workflow.

​
Good starter routines

  • Daily calendar, email, and Slack briefing
  • Weekly pipeline risk check
  • Invoice and receipt forwarding
  • Meeting follow-up drafting
  • New lead deduplication and enrichment
  • Competitor or target account monitoring