# Routine Library — 10 Ready to Paste A **routine** is a saved job with its own instructions. It fires two ways: on a **schedule** (a clock decides) or on a **trigger** (something happening decides). **How to create one:** just say it in chat. The bot writes the routine itself and you can open and edit it. Or open the bot's details panel → **Create Routine** → fill in Name, Instruction, and **When to run**. **The real trigger list** (from the app's own "when to run" menu): - On a schedule - Slack message - Git event - Teams message - Linear issue - Sentry alert - PagerDuty incident > ⚠️ **Trigger gotcha:** the bot can only hear Slack channels its app has been invited to. It gives you the exact invite command — run it once in the channel and the trigger goes live. --- ## 1 · Morning brief **Name:** `Morning brief` **When:** Schedule — weekdays, 7:00am **Instruction:** ``` Look at my calendar and my email. Send me a short plan for the day: what's on, what needs a reply, and what to protect. Tell me where the day is overloaded and what to move. Read only — never reply to anything. ``` --- ## 2 · Inbox to board **Name:** `Inbox to board` **When:** Schedule — daily, 7:30am **Instruction:** ``` Read my inbox. Pull out the things that are actually tasks and add them to my board with a due date and a priority level. Skip newsletters, receipts and automated mail. List anything that needs a reply from me personally. ``` --- ## 3 · Monday invoice reconciliation **Name:** `Monday invoice reconciliation` **When:** Schedule — Mondays, 8:00am **Instruction:** ``` Go through last week's invoices. Mark what's been paid, what's overdue, and what's still a draft. Draft a polite chase email for anything more than 14 days overdue and leave it in drafts for me. Post the summary to my board. ``` --- ## 4 · Daily competitor scan **Name:** `Daily competitor scan` **When:** Schedule — daily, 8:00am **Instruction:** ``` Scan the competitor channels and sites in my space, find what is taking off this week, and load the five strongest ideas into my board with a one-line angle for each. Use Firecrawl if a page won't read cleanly. ``` --- ## 5 · 5pm meeting sweep **Name:** `5pm meeting sweep` **When:** Schedule — weekdays, 5:00pm **Instruction:** ``` Pull today's meeting notes. Extract every action item and load it into the right project board with the right person assigned and a due date. Client actions to the client board, content actions to the content board. If ownership is unclear, put it on my list and say so. ``` --- ## 6 · Invoice keyword trigger **Name:** `Invoice mentioned` **When:** Trigger — Slack message *(or run it as a 30-minute schedule over Gmail if your invoices arrive by email)* **Instruction:** ``` When a client message mentions an invoice, payment, receipt or refund, pull the details, generate the invoice in my house style, and draft the reply with it attached. Log it on the board. Leave the reply as a draft — never send. ``` --- ## 7 · Sponsorship / inbound deal watch **Name:** `Deal watch` **When:** Trigger — Slack message on your inbound channel **Instruction:** ``` When a message lands that looks like a sponsorship, partnership or inbound deal, summarise it for me straight away: who, what they want, what they're offering, and any deadline. Add it to my board under Inbound. Don't reply to them. ``` *Invite the bot's app to that channel first or it hears nothing.* --- ## 8 · Weekly community update **Name:** `Weekly community update` **When:** Schedule — Fridays, 3:00pm **Instruction:** ``` Pull what shipped this week from my board and my notes. Draft a short community update in my voice: what's new, one thing worth trying this week, and one question to get replies. Leave it as a draft for me to post. ``` --- ## 9 · Weekly report pack **Name:** `Weekly report pack` **When:** Schedule — Fridays, 4:00pm **Instruction:** ``` Build this week's client report: what was delivered, what moved, what's blocked, and what's next week. Pull numbers from the connected dashboards rather than guessing. Put the draft on the board and tell me what's missing. ``` --- ## 10 · Build health check **Name:** `Build health check` **When:** Trigger — Git event *(or Sentry alert)* **Instruction:** ``` When a build fails or an error spike lands, read the log, summarise the likely cause in plain English, and post it with the failing file and line. Don't push any fixes — just tell me what broke and where. ``` --- ## Two habits that keep routines useful 1. **Say it in chat first.** Mention that you want something weekly, and the bot will usually create the routine itself. Then open it and tighten the wording. 2. **Prune monthly.** Routines are cheap to make and easy to forget. Anything that hasn't produced something you used in a month should be switched off — it's also the fastest way to stop burning weekly usage. --- *Part of the Grok Bot AI Full Course — *