Weekly GitHub Issue Summary to Slack via n8n Cron Workflow

Get a weekly GitHub issue status update in Slack—automatically, every Monday at 9:00 AM

This n8n Cron workflow pulls your GitHub issues, calculates how many are currently open vs. closed, and posts a clean weekly issue count summary directly to a Slack channel so your team stays aligned—without manual reporting.

What this workflow does

• Runs on a schedule: Starts every Monday at 9:00 AM using an n8n cron trigger.
• Fetches GitHub issues: Retrieves all issues from your selected GitHub owner/repository.
• Counts issue states: Processes the results to determine totals for open and closed issues.
• Builds a weekly summary: Prepares the report including totals and the current date.
• Posts to Slack: Sends the final summary to your chosen Slack channel using a Slack webhook or bot token, making the update visible to the whole team.

Use cases

• SaaS operators who want a simple weekly pulse on development health via GitHub issue reporting in Slack.
• Automation engineers standardizing recurring reporting with n8n Cron workflows.
• Teams that need consistent visibility into open vs. closed GitHub issues for sprint planning and triage.

Technical details

• Cron trigger for Monday 9:00 AM scheduling
• GitHub node to fetch issues from the configured owner/repo
• Function node to count open and closed issues and format the message
• Slack node using a Slack webhook or bot token to post to a specified channel

Setup

• Add GitHub credentials with access to the target repository, and select the correct owner/repo in the GitHub node.
• Add Slack credentials, and ensure the workflow can post to the destination channel (e.g., #team).
• Adjust the Slack message text and channel to match your preferred weekly report format.