Skip to content

Daily Briefing: Let the Bot Watch Your Slack, Email, and Calendar ​

💡 One-sentence summary: Use Grok Bot to build your AI daily briefing—automatically watching Slack, email, and calendar, reporting only what relates to your priorities and flagging what awaits your decision.

This is the first lesson of Route A (workplace), corresponding to the official use-cases page's 8 roles, specifically the Chief of staff role. The official positioning for it is: have a change summary with source links—not "tell you everything," but "only tell you about the changes that need your attention, with every item clickable back to its source."

The whole lesson takes about 12 minutes and walks through the official six-step method in full: duties into the description → connect apps → trial run with the starter prompt → feedback-based noise reduction and saving as a skill → schedule as a routine → hold the approval line.

What You'll Be Able to Do After This Lesson ​

  • Build a "Chief of Staff" Bot: connect Slack, email, and calendar, and produce a daily change summary with source links
  • Make the briefing report only what relates to your priorities: each item notes its source, why it matters, a suggested next step, and whether it awaits your decision
  • Use the "mark useful vs. noise" feedback loop to raise the signal-to-noise ratio, and save the workflow as a reusable skill
  • Schedule the briefing as a routine that shows up on time every workday morning—executed in the cloud, running even with your laptop closed, while outgoing actions still stay behind approval

Why Use Grok Bot Instead of Web-Based AI? ​

CapabilityWeb-Based AIGrok Bot
Can see your information sources❌ You have to copy and paste Slack logs and emails yourself✅ After connecting Slack, Gmail/Outlook, and Google Calendar, it reads them on its own
Remembers your priorities❌ You have to re-explain the context in every conversation✅ Duties are written into the Bot description, and context accumulates across conversations
Delivers the briefing on time every day❌ The web page won't come find you on a schedule✅ The routine triggers on schedule, executes in the cloud, and runs even with your computer closed
Every item comes with its source❌ Recounts from model memory, sources hard to verify✅ The official positioning is "a summary with source links," with every item noting its source
Sends messages and edits schedules for you❌ Can only give you text suggestions✅ It can, but by default it stops at drafts behind approval, acting only when you release it

Your Current Struggle ​

  • You get to your desk in the morning, scan through unread Slack, new emails, and calendar changes, and an hour is gone—and you don't dare skip any of it, afraid of missing the one message calling on you by name
  • You've tried having AI help with summaries, but every day you have to copy dozens of messages into the chat box and re-explain "what I'm working on and what matters"
  • Decisions that truly need your sign-off are buried in the information stream, and by the time you scroll past them the best moment has already passed

When to Use This Technique ​

When you need to:

  • Know "what happened from yesterday until now, and which parts concern me" before starting work each day
  • Compress "scanning every channel" into "reading one summary with sources"
  • Have important changes show up in front of you on time with context, instead of being buried in unread items

And you don't want to:

  • Open Slack, your inbox, and your calendar one by one to dig through records yourself
  • Copy and paste your work into a web chat box every day and re-explain the context

🎒 Preparation Before Starting ​

  • Read 3.2 Skills and Teaching—step 4 of this lesson saves the briefing workflow as a skill, and this is also the common prerequisite for all Route A scenarios
  • Have a Bot you can assign tasks to: if you don't have one yet, first go to 1.5 Create Your First Bot
  • Connect the three apps to watch: Slack, Gmail (or Outlook), and Google Calendar—see the 5-step connection method in 2.5 Connect Apps
  • Prepare a document listing your current priorities (OKRs, quarterly plans, or this week's goals all work)—the Bot uses it as the filtering criterion
  • About 12 minutes, plus one round of manual feedback after the first briefing comes out

Follow Along ​

Step 1: Write the Chief-of-Staff Duties into the Bot's Description ​

Why: The first step of the official six-step method is to write the duties, data sources, output format, and standing boundaries into the Bot's description—this is what it relies on every day to understand its job.

How: Create or open a Bot (sidebar + → Create a Bot), and write the description like the following, adapted to your actual situation:

You are my chief of staff, responsible for the daily AI daily briefing.
Data sources: the Slack, Gmail, and Google Calendar I've connected, plus the priorities document I provide.
Output format: a change summary with source links, each item noting its source, why it matters, the suggested next step, and whether it needs my sign-off.
Standing boundaries: summarize only; do not send messages or modify meetings; explicitly state any data sources you cannot read, and never pad with stale data.

You should see: After saving the description, you can see this statement of duties on the Bot's detail page. From then on, no matter which conversation you assign work in, it operates according to this positioning.

Step 2: Connect Slack, Email, and Calendar ​

Why: the briefing's facts can only come from the apps you connect — channels the Grok Bot cannot read never make it into the briefing.

How: connect the three apps one by one:

  1. Open Connect apps in the sidebar, search for Slack and add it
  2. When the Bot asks for Authorize / Authenticate, complete the login and authorization in your browser
  3. If the authorization is interrupted, click Reconnect (on the app) or Reopen (on the connection card in the chat) to get back to the login page
  4. Confirm that the app appears under Installed
  5. Repeat for Gmail (or Outlook) and Google Calendar

You should see: all three apps show Installed. Note that Added ≠ logged in — when Needs auth or Disconnected is shown, you must click Authenticate (on mobile it's Authorize) to re-authorize for it to count.

💡 This is the Grok Bot's unique value

A web-based AI can only see what you paste into it; the Grok Bot reads Slack, email, and calendar itself once apps are connected. Moreover, the OAuth token is stored in Cursor's connector backend — the Bot only calls tools and never handles your login credentials.

Step 3: Generate your first AI daily briefing with the official starter prompt ​

Why: the official starter prompt deliberately stops at a read-only review point — verify output quality first, then talk about automation.

How: send your priorities document to the Bot along with your message (drag it into the input box as an attachment, or paste a link), then send this localized Chinese version of the official Chief of staff starter prompt:

Review my activity from yesterday until now across my connected channels, inbox, calendar, and meeting notes.
Return only items related to the priorities in this document.
For each item, note: the source, why it matters, a suggested next step, and whether it needs my sign-off.
Do not send messages, and do not modify meetings.

If you only want it to look at certain apps, type @ in the chat to attach the apps to this task.

You should see: the Bot reads the connected apps one by one, then replies with a list — each item with its source, why it matters, the next step, and whether it's waiting for your sign-off; no messages are sent along the way.

Step 4: Mark what's useful and what's noise, and save the briefing workflow as a skill ​

Why: the official next step written after the starter prompt is "mark what's useful and what's noise" — your feedback determines the briefing's signal-to-noise ratio.

How: reply to the Bot directly about which items were useful, which were noise, and why (the "noise-reduction feedback" magic prompt below makes this easier). After two or three rounds of feedback, once output is stable, have it lock in the workflow:

Save the complete workflow you just used for the daily briefing as a skill named "Daily Briefing".
Requirements: aggregate my connected Slack, email, and calendar; keep only items related to my priorities document;
include a source link for each item; flag items that need my sign-off; do not send messages or modify meetings.

You should see: the Bot confirms the skill is saved, and from then on you can ask for it by name in any conversation — just say "run the Daily Briefing skill" to invoke it (@ is for Bots, groups, routines, and apps; it doesn't trigger skills). The private skill library is shared across all Bots — your other Bots can use it too. For saving details, see 3.2 Skills and teaching.

Step 5: Schedule the daily briefing as a timed routine ​

Why: the official recommendation is to schedule the briefing at a time you'll actually have time to read it — the value of a briefing is showing up at the same time every day.

How: use one plain-language sentence to have the Bot create a routine (the official example uses exactly this pattern):

Every weekday at 8:00, run the "Daily Briefing" skill: aggregate my connected Slack, email, and calendar
changes since yesterday, and post the briefing with source links to this chat.
If a data source can't be reached, report the failure directly — don't patch it with stale data.

The Bot will first confirm 6 items with you: which Bot is responsible, the schedule and time zone, input sources, expected results, approval boundaries, and what to do when a data source is missing. Once it's created, open the routine and check When to run — it shows the saved schedule in plain language; if it's not what you intended, click Edit to have the Bot change it.

You should see: the routine appears in this Bot's routines list. Don't miss these three official details:

  • A new routine only runs at the next scheduled time: a "daily at 8:00" created at 8:05 runs for the first time tomorrow at 8:00 — to verify right away, click Test
  • The time zone follows Settings → Bot → Timezone (Auto-detect follows your device) — if 8 doesn't look right, check here first
  • Routines run in the cloud, so closing your laptop doesn't affect them

For more scheduling details, see 3.3 Routines.

Step 6: Hold the approval line — briefings are automatic, sending is not ​

Why: the last step of the official six-step method: consequential external actions always stay behind approval.

How: you don't need to do anything — keep the defaults. Auto Review is on by default, outgoing emails and Slack messages come out as draft cards by default (Needs approval), and emails sent by routines always go to drafts waiting for you to click Send. Once the Bot is connected to Google Calendar it does have the ability to create and update events, but the official starter prompt explicitly says "do not modify meetings" — as for whether to grant that power, wait until the briefing has run stably for a few weeks.

You should see: what you receive on time each day is a summary; if you happen to ask the Bot to reply to messages or change your schedule, those actions appear as drafts or approval cards for you to release. For approval rule details, see 3.1 Approvals and Auto Review.

📋 Magic Prompts ​

📝 Daily Briefing (official starter prompt, structured version) ​

Expected result: the Bot replies with a list grouped by "waiting for your sign-off / just for your awareness", each item with a source link, and unrelated items filtered out.

## Role
You are my chief of staff, monitoring my information streams every day and putting together my daily briefing.
## Task
Aggregate changes in my connected Slack, email, and calendar since [lookback start], keeping only items related to the priorities document.
## Input
### Required
- Priorities document: [attach with the message or paste a link; state your current goals and their weights clearly]
- Lookback window: [e.g., from yesterday 9:00 until now]
### Optional
- Exclusions: [Channels, senders, or calendars you don't want to see?]
- Meeting notes: [Links to meeting notes that should be reviewed together?]
## Output specification
Split into two groups: ① Awaiting my decision ② For awareness only. Each item includes: source link, a one-sentence summary of the change, why it matters, and a suggested next step.
## Constraints
- ✅ Every item includes its source; explicitly state any channel that can't be read
- ✅ Discard items unrelated to priorities outright—don't pad the count
- ❌ Do not send any messages
- ❌ Do not modify any meetings or calendar events

📝 AI Weekly Report (Weekly Digest Edition) ​

Expected outcome: compress the week's daily briefings into a single AI weekly report—read the main themes first, then see what needs to be prepared in advance for next week.

## Role
You are my chief of staff; write this week's report for me.
## Task
Consolidate this week's daily briefings into one AI weekly report: first distill the week's main themes, then pick out from next week's calendar the items that need advance preparation.
## Input
### Required
- This week's priority document: [Attach with the message or paste a link]
### Optional
- Number of main themes: [For example: at most 5 items?]
- Output format: [Send directly in the chat, or organize into a Pages page?]
## Output specification
Three parts: ① This week's main themes (each with a source link) ② Ongoing items without results yet ③ Items in next week's calendar that need advance preparation.
## Constraints
- ✅ Base everything only on this week's briefings and real content in connected apps
- ✅ Every main theme includes its source; explicitly state any channel that can't be read
- ❌ Do not introduce speculation without sources
- ❌ Do not send it to anyone

🔧 Noise-Reduction Feedback (Tuning the Signal-to-Noise Ratio) ​

Expected outcome: the Bot updates the filtering criteria based on your feedback and writes them into the skill, so tomorrow's briefing is noticeably cleaner.

## Role
You are my chief of staff and have just sent me today's daily briefing.
## Task
Based on my feedback, update the criteria for judging "useful / noise" and write them into your daily briefing skill.
## Input
### Required
- Useful items: [List the items in today's briefing you found useful]
- Noise items: [List the items that wasted your time, and explain why]
### Optional
- New items to watch: [Things not reported today that you'd like to see going forward?]
## Output specification
First restate the new criteria you've summarized; update the skill only after I confirm.
## Constraints
- ✅ Write the criteria into the skill, taking effect starting tomorrow
- ✅ Only adjust the "useful / noise" judging criteria; don't change the output format or approval boundaries
- ❌ Don't mark every item as useful just to please me
- ❌ Do not send any messages

Checkpoints ✅ ​

  • Slack, email, and calendar in Connect apps all show Installed (not Needs auth / Disconnected)
  • The first briefing includes a source for every item, and no messages were sent and no meetings were modified
  • The briefing workflow is saved as a skill and can be invoked by name (e.g., "Run the daily briefing")
  • The routine's When to run shows your desired schedule, with the time zone matching Settings → Bot → Timezone
  • When the Bot wants to send something outward, it first produces a draft or approval card for you to release

Pitfall Warnings ​

❌ An app shows Needs auth, and that channel is missing from the briefing ​

Added ≠ logged in: if an app was added but authorization wasn't completed, the Bot can't read it. Open that app; if it shows Needs auth or Disconnected, click Authenticate (on mobile it's Authorize). A company Google account may also prompt Your admin needs to review Grok—an admin needs to mark Grok as trusted in the Google Admin console; see the steps in 2.5 Connect apps.

❌ The briefing becomes a running log full of noise ​

Usually the priority document is too vague, or wasn't provided at all—so the Bot reports everything. Give it a specific priority document, then use "noise-reduction feedback" daily to mark what's useful and what's noise. The Bot remembers this feedback, and within a few days the signal-to-noise ratio improves.

❌ The routine runs too frequently, burning a week's usage in one day ​

Each routine run consumes usage; the official docs explicitly warn that running once an hour or triggering on busy channels could burn a week's quota in a day. Once a day is enough for a daily briefing—run it for a few weeks until it's stable before considering a tighter schedule.

❌ No briefing at 8 a.m., so you assume the routine is broken ​

A new routine waits for the next scheduled time: a "daily at 8:00" created at 8:05 runs for the first time tomorrow at 8:00. To verify immediately, click Test. If it's still wrong, check the time zone: Settings → Bot → Timezone (Auto-detect follows the local device).

❌ Gmail was switched to a different inbox, but the briefing still reads the old one ​

Gmail connects to only one mailbox at a time. To switch, disconnect the current mailbox first, then authorize the other one—the Bot won't automatically follow your new mailbox.

Advanced Tips (Optional) ​

  • Event-triggered version: besides schedules, routines can also be triggered by events—Slack messages, GitHub/Linear/Sentry/PagerDuty events, emails sent to the Bot's dedicated mailbox, webhooks. Note two things: email triggers can be filtered by sender or domain, but not by subject; new emails don't automatically wake the Bot—you must set up a routine. See 3.3 Routines and 2.6 Bot's dedicated mailbox.
  • Archive briefings as Pages: have the Bot also organize each day's briefing into a Pages page (officially positioned as readable pages like reports and dashboards), stored in the Bot's Library—review the whole week on the weekend without scrolling through chat history. See 2.2 Files and reviewable outputs.
  • Swap the data sources for a new scenario: with the same six steps, replace Slack, email, and calendar with CRM, product usage, support tickets, and billing to get a ranked list of risk and upsell signals for A5 Account health.

Lesson Summary ​

  • ✅ One "chief of staff" Bot + three types of data sources (Slack, email, calendar + priority document) producing a source-linked AI daily briefing every day
  • ✅ Start with the official starter prompt: read-only, no modifications; each item notes its source, why it matters, the next step, and whether it awaits your decision
  • ✅ Feedback for noise reduction → save as a skill → schedule as a routine: appears on time every weekday morning, executed in the cloud
  • ✅ The safety line never wavers: external actions like sending messages or modifying meetings always stay behind drafts and approvals
Key itemValue in this lesson
Bot roleChief of staff—change summaries with source links
Connected appsSlack, Gmail (or Outlook), Google Calendar
Briefing filter criteriaYour priority document
skill"Daily Briefing" (name it yourself, invoke it by name, shared across all Bots)
routineevery weekday morning at 8:00 (example); see Settings → Bot → Timezone for the time zone
Approval lineOutgoing emails/Slack messages start as draft cards; emails sent by routines always stay as drafts

Next Lesson Preview ​

Next Lesson A2 Expense Reconciliation: Still the same six steps, but swap the information sources to the expense system, email, and finance spreadsheets, and let the Bot reconcile invoices and bills for you every week. You will learn:

  • Turn the expense policy document into reconciliation standards, with every anomaly accompanied by a policy citation
  • Make "totals match the source" a hard validation check
  • Generate a follow-up draft for each colleague with missing items — as always, it stops at the review point and is not sent automatically
gaodong.aiAboutPrivacyContact

Independent tutorials, not affiliated with any product mentioned. Product names and trademarks belong to their owners. Check official pages for prices and policies.