Daily Standup Digest to Slack Channel
Compile team updates into a single daily message so you never miss critical blockers.
Nora monitors Slack thread activity and creates a daily digest summarizing key messages, decisions, and action items from your team channels. Automatically posts the digest to a designated #standup channel every morning, keeping everyone aligned without meeting overhead.
Every morning at 9:00 AM, Nora reads the message history across designated team channels from the preceding 24 hours. It extracts completed tasks, key decisions, and identified blockers based on keyword matching and context. Nora formats these findings into a single threaded Block Kit message and posts it to the #standup channel. The digest includes message counts per project and highlights critical blockers prominently.
The operations manager reviews the consolidated digest to identify which blockers require immediate attention. They decide how to allocate resources to unblock team members and whether any decisions need broader communication. The manager no longer spends the first hour of the day skimming multiple project channels to piece together the team's status, but they retain full control over how to resolve the surfaced issues.
Runs daily at 9:00 am using Slack, run by your Operations Manager.
How it works
- Trigger the morning schedule — At 9:00 AM daily, the cron schedule initiates the automation. Nora connects to the Slack workspace using the stored OAuth bot token and retrieves the list of target team channels configured for monitoring.
- Read channel message history — Nora calls the Slack API to pull all messages and thread replies posted in the target channels over the last 24 hours. It maps the message authors to workspace members using the users list.
- Extract tasks and decisions — The automation evaluates the text of each message. It identifies completed work, decisions made, and active discussions, separating routine chatter from material project updates.
- Identify critical blockers — Nora scans the filtered messages for keywords indicating someone is stuck. It evaluates the context around these terms to confirm if it represents an actual blocker rather than a casual complaint.
- Handle quiet channels — If a monitored channel has no activity or only contains non-work conversation for the period, Nora notes the channel as inactive for the day. It omits empty sections from the final digest rather than posting zero-counts.
- Format and post digest — Nora compiles the extracted information into a structured summary using Block Kit formatting. It posts this daily digest to the designated #standup channel as a new message, applying threaded formatting for subsequent discussion.
What this replaces
A team lead or operations manager opens Slack at the start of their day. They manually click through five to ten different project channels, scrolling back to find where they left off yesterday. They read the intervening messages, take notes on what was finished, spot who is waiting on whom, and type a summary into the main team channel.
- Scroll through history in multiple project channels to find new messages.
- Read threads to identify completed tasks and final decisions.
- Note instances where a team member states they are blocked.
- Draft a summary message consolidating updates across all projects.
- Post the summary to the main team channel.
Rough estimate rather than a measured figure: about 45 minutes a day, on the basis of checking 8 channels and spending 5-6 minutes reading and summarizing each one.
What it needs to run
Accounts and plans
- A Slack workspace with permission to install external applications.
- A dedicated #standup channel where the digest will be posted.
Access it asks for
- chat:write to send the compiled daily digest to the target channel.
- users:read to list workspace members and match them to message authors.
- Permission to read message history to pull the past 24 hours of conversation.
What Nora reads
- Message text and thread replies from the configured team channels.
- Timestamps to filter for the last 24 hours of activity.
- Workspace member lists to attribute updates to specific users.
What Nora writes
- A single new daily message in the designated #standup channel.
- Threaded replies on the digest message if the summary is long.
When it goes wrong
- The Slack API rate limits the request during a high-volume message pull. Nora pauses execution and respects the Tier 3 rate limit retry headers. It resumes pulling message history once the window resets, delaying the digest posting slightly until all channels are processed.
- A monitored channel is archived or deleted by a workspace admin. The API returns an error when Nora attempts to read the channel. The automation skips the missing channel for that day's digest and sends a direct message to the operations manager noting the configuration change.
- The OAuth bot token expires or is revoked. Nora halts the run immediately upon receiving the authentication error. It sends an email to the account owner requesting they reconnect the Slack workspace to restore access.
- Message activity contains no identifiable tasks, decisions, or blockers. Nora determines there is nothing material to report. It posts a brief message to the #standup channel stating that no major updates were detected in the monitored channels for the period.
Who this is for
Worth it if
- Operations managers at 10-30 person remote companies where project updates are scattered across dozens of channels.
- Engineering leads who want to spot blocked developers before the afternoon without scheduling daily synchronous meetings.
- Cross-functional teams that rely heavily on asynchronous Slack threads for making product decisions.
Not worth it if
- Teams with fewer than five members where everyone already reads every message in a single general channel.
- Organizations that mandate strict daily video standups, making an asynchronous written summary redundant.
- Workspaces where project management happens entirely in external tools and Slack is only used for casual conversation.
A worked example
A 15-person software agency monitors six client-specific Slack channels. Nora is instructed to read messages from the past 24 hours, extract blockers and completed deployments, and post the summary to the #engineering-standup channel at 9:00 AM.
Daily Standup Digest: Oct 24 Channels monitored: 6 | Active discussions: 42 messages Critical Blockers: - @sarah is blocked on the API integration for Client A (waiting on third-party credentials). Key Decisions: - @david decided to postpone the database migration for Client C until the weekend maintenance window. Completed Tasks: - @mike merged the authentication fix for Client B. - @elena finalized the design assets for the new marketing site. Reply in thread to discuss any of these items.
Frequently asked questions
How do I change which channels are included in the daily digest?
You tell Nora in plain language via web chat or WhatsApp. If you start a new project and want its channel monitored, you simply message Nora to add the new channel to the standup digest. Nora updates the configuration immediately and includes the new channel in the next morning's run.
Will Nora read private messages or direct messages between team members?
No. Nora only reads the specific channels you explicitly instruct it to monitor. Because your automation runs in your own dedicated single-tenant instance, your data stays isolated. It cannot access direct messages or private channels unless you invite the bot into a private channel and tell Nora to include it.
What happens if someone uses a blocker keyword jokingly?
Nora evaluates the surrounding context of the message rather than relying on strict keyword triggers alone. If a team member says they are stuck in traffic, Nora recognizes this is not a project blocker and excludes it from the critical blockers section of the digest.
Can I change the time the digest is posted?
Yes. You can ask Nora to adjust the schedule to fit your team's routine. If your team spans multiple time zones and prefers the digest at 11:00 AM, you inform Nora of the new time via chat, and the cron schedule is updated for all future runs.
Connects to
Related automations
- Extract Action Items from Slack Threads to Task Board — Turn meeting discussions into tracked tasks automatically.
- Daily Sprint Health Check & Burndown Alert — Catch sprint problems on day 2, not day 10.
- Auto-Link GitHub PRs to Jira Tickets — Stop copying & pasting issue numbers into PR descriptions.
- Post-Appointment Survey via SMS — Get instant feedback from customers right after their appointment via SMS
- Auto-Respond to FAQ in Slack — Answer common questions instantly in Slack threads so your team stays unblocked.
- Smart DM Follow-Up Reminders — Never lose track of messages awaiting response.
- Route Customer Feedback to Relevant Teams — Automatically send customer feedback to the right Slack channel for action.
- Automated New Hire Onboarding in Slack — Run every new hire through the same onboarding checklist, tracked automatically.