Nebula is in beta — new features are shipping every week.
NebulaNebula

Digest Reports

Generate AI digest reports with Nebula — daily or weekly Slack channel summaries organized by topic with key decisions and action items highlighted.

What you'll build

Nebula reads through your busiest Slack channels, groups messages by topic, highlights decisions and action items, and posts a clean digest so your team can catch up in 30 seconds instead of scrolling through hundreds of messages.

What to say

You

Summarize everything that happened in #product and #engineering on Slack this week. Group by topic and highlight decisions. Post to #weekly-recap.

Read Slack MessagesSlack Agent

Reading #product and #engineering... Found 142 messages this week.

Nebula
Nebula

Digest posted to #weekly-recap. 3 decisions highlighted, 5 topics covered, 4 action items flagged.

Adjust the channels, timeframe, and how you want the summary organized. You can ask for daily digests, weekly recaps, or summaries of specific date ranges.

What happens

Nebula reads all messages from the target channels

Your Slack Agent fetches every message from #product and #engineering within the specified timeframe. It pulls the full message text, who posted it, and any thread replies so nothing important gets missed.

Messages are grouped by topic

Nebula reads through all 142 messages and clusters them into logical topics like "mobile redesign," "API migration," and "Q2 planning." Related threads and side conversations get rolled into the right group.

Decisions and action items are highlighted

Within each topic, Nebula identifies anything that looks like a decision ("we agreed to ship v2 on Thursday") or an action item ("@sam will update the staging environment by EOD"). These get called out explicitly so they don't get buried.

The digest is posted to your recap channel

Nebula compiles everything into a clean summary and posts it to #weekly-recap. It looks something like this:


Weekly Digest | #product + #engineering | Feb 24 -- Feb 28

Mobile Redesign (34 messages)

  • Decision: Going with the tab-based navigation. Design approved by @lisa.
  • Action item: @sam to update Figma prototypes by Monday.

API Migration (28 messages)

  • Decision: Deprecating v1 endpoints on April 1. Migration guide drafted by @alex.
  • Action item: @jordan to notify external partners by March 7.

Q2 Planning (19 messages)

  • Decision: Prioritizing self-serve onboarding over enterprise features.
  • Action item: @maya to finalize the roadmap doc and share by Friday.

Bug Fixes (12 messages)

  • Fixed: Authentication timeout on mobile (shipped by @alex).
  • In progress: Dashboard loading issue being investigated by @jordan.

General (49 messages)

  • Team lunch scheduled for Thursday. Office hours moved to 3 PM.

Make it automatic

You

Do this every Friday at 4 PM.

Create Trigger

Creating scheduled trigger: every Friday at 4:00 PM UTC. Task: read #product and #engineering for the week, group by topic, highlight decisions and action items, post digest to #weekly-recap.

Nebula
Nebula

Your trigger is live. Every Friday at 4 PM, I'll read both channels, compile the digest, and post it to #weekly-recap. You can pause or edit this from the Triggers page.

Nebula creates a scheduled trigger that runs automatically each Friday. You can view, pause, or delete it from the Triggers page in the sidebar.

Connect your integrations

This recipe uses Slack. Add the Nebula Slack bot from the Integrations page, then invite the bot to the channels you want summarized and the channel where you want the digest posted.

On this page