Daily Slack channel summary
Every weekday at 9am, a digest of your key Slack channels — decisions, open questions, action items with owners, and anything awaiting a reply — posted to a channel and emailed.
Weekdays at 9:00 AMProductivity Emailed to you
Use this routine →Opens prefilled — review and save.
Works with
The instructions
Every weekday at 9am, read the Slack channels I care about and give me one digest of what happened since yesterday. 1. Read the recent message history of the channels I pick (the ones I'm a member of) — pull messages posted since the previous run, and read the thread replies on any busy threads so you don't miss decisions buried in replies. Resolve author IDs to people's names so every item is attributed. If it helps, search for keywords I flag (e.g. "decision", "blocker", "ship") across those channels to catch things outside the main flow. 2. Sort what you find into four buckets: Decisions made, Open questions (still unanswered), Action items (with the owner named, and a due date if one was stated), and Needs a reply (messages addressed to me or the team that nobody has answered). Label each item with the channel it came from. Skip noise — reactions-only chatter, bot pings, and resolved threads. 3. Post one summary message to the channel I choose. It posts on my behalf, under my name — so write it as a clear, neutral digest. Post exactly one message: do not reply in threads, do not DM anyone, do not react, and do not change any channel settings — reading and that single post are all this routine should ever do. Keep it tight and skimmable: a one-line headline with the single most important thing, then the four buckets as short bullets, each tagged with its channel. If a channel had no activity since the last run, or if you can't read a channel I picked, say so plainly instead of guessing or padding the summary.
What a run emails you
Slack digest — Mon 29 Jun, since Fri 5pm Heads up: launch date moved to 11 Jul — 2 action items land on you. Decisions made • #product — Ship v2 onboarding behind a flag first; full rollout after the 11 Jul launch (Priya N.) • #eng — Dropping the legacy import path; Dana K. to remove it this sprint Open questions • #marketing — Who owns the launch blog post? Asked Fri, still no answer • #product — Are we keeping the old pricing page live during rollout? Action items • You — Sign off on the launch checklist by Wed (Sam R.) • You — Reply to legal on the ToS change (raised in #general) • Dana K. — Remove legacy import path this sprint Needs a reply • #general — Sam R. tagged you Fri 4pm about the launch checklist — no reply yet Read 5 channels · posted to #daily-digest on your behalf.
How it works
- Attach your Slack connection and pick the channels to watch — the routine reads recent message history (and thread replies) only in channels you're a member of, using the read access you granted, then posts one digest to the single channel you choose. It runs on your behalf under your own name, not as a separate bot.
- It groups the activity into decisions, open questions, action items with named owners, and anything still awaiting a reply, attributing each item to a person and tagging it with its source channel — so the digest is a real handoff, not a raw message dump.
- Keep "Email me the result" on to get the same digest in your inbox every morning, even on days you don't open Slack.
Make it yours
- Change which channels it watches and which one it posts to — point the digest at a team channel, a private project channel you're in, or just back to yourself.
- Tune the buckets and keywords — add a "risks" section, flag terms like "blocker" or "decision" to surface, or tell it to ignore a noisy channel.
- Posting one message is a deliberate design choice, not a limit — by default it never replies in threads, DMs anyone, or reacts; widen or narrow that in the instructions if your team wants it.
Your connections stay yours: tokens are encrypted at rest, and the agent only reads the channels you pick and posts the one message you ask for — nothing more.
Run “Daily Slack channel summary” on autopilot
Copy it to your account, tweak the details, and it runs weekdays at 9:00 am.
Use this routine →More Productivity templates
New Google Drive docs digestProductivity
A weekday-morning Slack digest of Google Drive files created or edited in the last day.
Weekdays at 8:00 AM
Weekly Airtable rollupProductivity
Every Friday, roll up the week's Airtable changes and email a clean summary to your team.
Fridays at 5:00 PM
Weekly overdue Asana tasks roundupProductivity
A Monday email of every overdue and due-this-week Asana task, grouped by owner.
Mondays at 9:00 AM
Daily standup doc in CraftProductivity
Every weekday at 7am, create a fresh, dated standup note in Craft — pre-structured with Yesterday / Today / Blockers, and primed with your calendar for the day.
Weekdays at 7:00 AM