Skip to main content

Send daily stale PR review digest with GitHub and Slack

Workflow preview

Workflow preview
100%
Send daily stale PR review digest with GitHub and Slack preview
Open on n8n.io

1. Workflow Overview

Quick Overview This workflow runs every weekday at 9 AM, checks open pull requests across configured GitHub repositories, calculates how long each PR has been waiting on review activity, and posts ...

Best for

  • DevOps automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.if, n8n-nodes-base.slack

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Monfort N. Brian | 宁俊.

Original n8n.io source

1.1 Workflow description

Title
Send daily stale PR review digest with GitHub and Slack
Workflow name
Send daily stale PR review digest with GitHub and Slack

Quick Overview

This workflow runs every weekday at 9 AM, checks open pull requests across configured GitHub repositories, calculates how long each PR has been waiting on review activity, and posts a ranked review-lag digest to a chosen Slack channel.

How it works

  1. Runs on a weekday schedule at 9:00 AM and loads the repository list, staleness threshold, draft filtering option, and target Slack channel.
  2. Queries the GitHub API for open pull requests in each configured repository.
  3. Filters out draft PRs (optional), normalizes PR fields, and fetches each PR’s review history from the GitHub API.
  4. Calculates review-lag metrics per PR (age, last review time, current review status, and whether it is stale based on the configured days threshold).
  5. Aggregates and ranks PRs by review lag, then builds a Slack-formatted digest grouped by PR author.
  6. Posts the digest to Slack only when there are PRs to report.

Setup

  1. Add GitHub credentials for the HTTP Request nodes (a Personal Access Token in an HTTP Header Auth credential with access to the target repositories).
  2. Add a Slack OAuth2 connection and ensure the workflow can post to the target channel.
  3. Update the configuration values (repositories, stale_days, slack_channel, and exclude_drafts) to match your GitHub org and Slack workspace.
  4. Confirm the schedule trigger cron expression (0 9 * * 1-5) matches your intended timezone and weekdays.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 6 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 7 - When Weekday at 9am

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.3

Block 8 - Set PR Monitor Config

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 9 - Expand Repos to Items

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 10 - Fetch GitHub Open PRs

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 11 - Parse PR Response Data

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 12 - Fetch PR Review Data

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 13 - Calculate Review Lag

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 14 - Build Slack Digest

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 15 - Check PRs Found

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.3

Block 16 - Send Digest to Slack

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.4

3. Summary Table

Workflow Send daily stale PR review digest with GitHub and Slack
Complexity advanced
Nodes 16
Categories DevOps
Author Monfort N. Brian | 宁俊
Published 02 Jun 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/16068/16068.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Send daily stale PR review digest with GitHub and Slack do?

Quick Overview This workflow runs every weekday at 9 AM, checks open pull requests across configured GitHub repositories, calculates how long each PR has been waiting on review activity, and posts ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your DevOps use case.