Post GitHub Digest To Slack

OpenAISlack

Fetch yesterday's GitHub commits, merged pull requests, and closed issues, and post a ranked activity digest to your team's Slack channel daily.

GitHubSlackEngineering AnalyticsDaily Digest

What It Does

Posts a daily GitHub activity digest to your Slack channel every morning at 8 AM UTC. Covers all commits, merged pull requests, and closed issues from the past 24 hours across every repo your team has access to. The team sees it in Slack before standup starts.

Why It Matters

Engineering leads waste valuable time every morning piecing together what the team shipped yesterday. You check GitHub, ask in Slack, and scroll commit logs. By the time standup starts you still might not have the full picture. This workflow removes that completely. One message in Slack every morning tells you exactly what moved. No manual digging, no context switching.

How It Works

StepComponentAction
1Scheduled TriggerFires every day at 8:00 AM UTC.
2AI AgentFetches all GitHub commits, merged PRs, and closed issues from the past 24 hours.
3AI AgentFormats the retrieved data into a clean Slack digest with mrkdwn formatting.
4SlackPosts the digest directly to your configured channel.

What You Get

  1. All commits from the past 24 hours with author and repo context.
  2. All merged pull requests with clickable links and who merged them.
  3. All closed issues with links.
  4. Top contributor of the day highlighted.
  5. Quiet day message when there is no activity.

Who It Is For

  1. Engineering leads who run daily standups and need yesterday's summary ready.
  2. Staff engineers and tech leads managing multiple repositories.
  3. DevOps and platform teams monitoring activity across many repos.
  4. Remote and distributed engineering teams who need async visibility.

Setup

  1. Connect your GitHub account.
  2. Connect your Slack account and select the channel.
  3. Publish the workflow. The first digest posts tomorrow at 8 AM UTC.

Customize It

  1. Change the schedule to match your team's timezone (e.g., change cron to 0 7 * * * for 7 AM UTC delivery).
  2. Edit the AI Agent prompt to add repository filters or focus on specific teams.
  3. Add a fourth category to track deployments separately.

Timezone Note

  1. 8:00 AM UTC is 1:30 PM IST and 3:00 AM EST.
  2. For 8 AM IST delivery, change the cron expression to 30 2 * * *.

Built By

Shamanth Kumar M, Staff Technical Program Manager with 14+ years in engineering delivery. Building intelligent systems that replace manual work, from sprint tracking to DevOps pipelines and delivery health dashboards.

Want to showcase your own workflows?

Become a Needle workflow partner and turn your expertise into recurring revenue.

Try Needle today

Streamline AI productivity at your company today

Join thousands of people who have transformed their workflows.

Agentic workflowsAutomations, meet AI agents
AI SearchAll your data, searchable
Chat widgetsDrop-in widget for your website
Developer APIMake your app talk to Needle
    Needle LogoNeedle
    Like many websites, we use cookies to enhance your experience, analyze site traffic and deliver personalized content while you are here. By clicking "Accept", you are giving us your consent to use cookies in this way. Read our more on our cookie policy .