Review n8n workflows from Slack with Claude Opus and GitHub skills

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Quick overview A Slack bot that reviews any n8n workflow on demand. Mention it or DM it a workflow URL and it replies in thread with a graded review, plain English overview, and findings tiered as ...

Best for

Engineering automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.slacktrigger, n8n-nodes-base.filter, n8n-nodes-base.slack, n8n-nodes-base.set, n8n-nodes-base.if, n8n-nodes-base.n8n, n8n-nodes-base.httprequest, n8n-nodes-base.splitout

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Liam McGarrigle.

Original n8n.io source

1.1 Workflow description

Title: Review n8n workflows from Slack with Claude Opus and GitHub skills
Workflow name: Review n8n workflows from Slack with Claude Opus and GitHub skills

Quick overview

A Slack bot that reviews any n8n workflow on demand. Mention it or DM it a workflow URL and it replies in-thread with a graded review, plain-English overview, and findings tiered as Must Fix, Should Fix, and Nice to Have.

How it works

Triggers when the bot is @mentioned in Slack or receives a direct message.
Adds an :eyes: reaction, extracts a /workflow/<id> from the message text, and validates that a workflow ID is present.
Uses the n8n API to fetch the top-level workflow JSON and pulls the workflow review checklist and skills file index from the public n8n-io/skills GitHub repository.
Detects any Execute Workflow references in the workflow, fetches those direct subworkflow JSONs via the n8n API, and aggregates them into a single payload.
Sends the workflow JSON, subworkflows, checklist, and available skill file paths to an OpenRouter-hosted model that can fetch additional skill markdown files as needed.
Removes the :eyes: reaction and posts the graded review back to the originating Slack thread as a Block Kit message, or posts a threaded error message if the URL, API fetch, GitHub fetch, or agent run fails.

Setup

Connect a Slack API credential with permission to receive app mentions/DMs, add reactions, and post threaded replies, and configure the trigger to watch the intended workspace.
Add an n8n API credential that can read workflows, and ensure the n8n host in your workflow URLs matches the instance the credential points to.
Add an OpenRouter API credential and choose the model you want to use for the reviewer agent and (optionally) the structured-output fixer.
Install the Slack app, enable event subscriptions for app_mention and direct messages, and invite the app to any channels where you want to request reviews.
If your environment restricts outbound HTTP, allow access to raw.githubusercontent.com and api.github.com so the workflow can load the n8n-io/skills checklist and file index.

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 - Slack: @mention or DM

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

Block 2 - Keep mentions and DMs

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

Block 3 - Add Eyes Reaction

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

Block 4 - Parse URL

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

Block 5 - Valid URL?

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

Block 6 - Get Top-Level Workflow

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

Block 7 - Remove Reaction (Bad URL)

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

Block 8 - Post Error: Bad URL

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

Block 9 - Remove Reaction (Fetch Failed)

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

Block 10 - Post Error: Fetch Failed

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

Block 11 - Fetch Review Checklist

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

Block 12 - Remove Reaction (Checklist Failed)

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

Block 13 - Post Error: Checklist Failed

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

Block 14 - Extract Subworkflow IDs

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

Block 15 - Split Out Subworkflow IDs

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

Block 16 - Get Each Subworkflow

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

Block 17 - Aggregate Subworkflows

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

Block 18 - Combine Branches

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 19 - Empty Subworkflows

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

Block 20 - Build Agent Payload

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

Block 21 - Reviewer Agent

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3.1

Block 22 - Get Skill File

Type / Role: n8n-nodes-base.httpRequestTool - httpRequestTool
Config choices: Version 4.4

Block 23 - Block Kit Output Parser

Type / Role: @n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices: Version 1.3

Block 24 - Remove Reaction (Agent Failed)

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

Showing the first 24 of 43 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Review n8n workflows from Slack with Claude Opus and GitHub skills
Complexity	advanced
Nodes	43
Categories	Engineering, AI Summarization
Author	Liam McGarrigle
Published	22 May 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/15918/15918.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
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. 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.

Download workflow JSON Original n8n.io source Engineering workflows AI Summarization workflows

Frequently asked questions

What does Review n8n workflows from Slack with Claude Opus and GitHub skills do?

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 Engineering, AI Summarization use case.

Liam McGarrigle

4 workflows

Nodes

n8n-nodes-base.slacktrigger n8n-nodes-base.filter n8n-nodes-base.slack n8n-nodes-base.set n8n-nodes-base.if n8n-nodes-base.n8n n8n-nodes-base.httprequest n8n-nodes-base.splitout

Complexity

advanced

Published 22 May 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/15918/15918.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Build self-improving agent skills with cognee

## Quick overview A self-improving loop for agent skills, powered by the cognee Verified Node. When a skill's review scores below your threshold, it proposes a rewrite, and you approve the before/after diff before it's applied. No code required. ## How it works 1. Execute your workflow. 2. Set the demo inputs (skill name, dataset name, skill procedure markdown, review task text, and the score threshold). 3. Ingest the skill into cognee. 4. Cognee reviews the skill’s performance and returns a JSON with a score and gaps. 5. If the score is below the threshold, the workflow requests a cognee improvement proposal for the skill. 6. The workflow retrieves the full proposal from cognee and builds a human-readable before/after diff. 7. If the proposal is approved, the workflow applies the improvement in cognee, fetches the updated skill, and outputs the updated procedure and diff. ## Setup 1. Create a cognee API credential in n8n and use it in all cognee nodes (Ingest Skill, Review Skill, Propose Improvement, Get Proposal, Apply Improvement, Get Skill). Information for the credential (URL and API key) can be found in your Cognee Cloud account. 2. Update the skill parameters (skill_name, dataset_name, skill_markdown, task_text, score_threshold, and approved) to match your use case. 3. Ensure the referenced cognee dataset name exists so the skill can be stored and retrieved consistently.

View

Orchestrate multi-agent energy optimization with OpenAI GPT and Claude

## Quick Overview This workflow runs manually to orchestrate multi-agent analysis for a thermodynamic system, using OpenAI and Anthropic models to interpret sensor inputs, optimize energy usage, plan and execute tasks, validate results, and send an HTTP alert if validation fails. ## How it works 1. Starts when you manually trigger the workflow with initial system state, temperature, energy budget, and a task queue. 2. Uses OpenAI (GPT-5-mini) to analyze the provided sensor context, detect anomalies, and output structured sensor readings with confidence scores. 3. Uses OpenAI (GPT-5-mini) plus a calculator and custom energy-analysis code tool to compute efficiency/entropy metrics and propose an optimized energy allocation. 4. Uses OpenAI (GPT-5-mini) to build an execution plan and energy estimate for the queued tasks based on the optimized budget and sensor state. 5. Uses Anthropic (Claude Sonnet) to execute the planned task sequence within the estimated energy limit and return structured outcomes and actual energy usage. 6. Uses Anthropic (Claude Sonnet) to validate thermodynamic compliance by comparing planned vs. actual energy and generating recommendations. 7. If validation passes, compiles a final system report and returns the final system state; if validation fails, generates recalibration parameters and posts a JSON alert to an external webhook endpoint. ## Setup 1. Add credentials for OpenAI (Chat) and Anthropic (Chat) so the Perception, Energy Optimization, Planning, Execution, Validation, and Recalibration agents can run. 2. Replace the placeholder alert webhook URL in the HTTP Request step and configure HTTP Header Auth credentials for the target alerting endpoint. 3. Provide the required input fields on trigger (systemState, temperature, energyBudget, and taskQueue) or adjust the prompts to match your data structure. 4. If your execution step needs real environment context, add or connect a node that supplies the referenced environment data (the workflow currently references “Fetch Environment Data” but does not include it).

View

Optimize maritime routes and disruption response with OpenAI and Slack

## Quick Overview This workflow runs every 15 minutes to pull vessel telemetry/AIS data, enrich it with port and weather context, and use OpenAI to detect disruptions, simulate route alternatives, and generate an executive briefing that requires human approval before notifying teams in Slack. ## How it works 1. Runs every 15 minutes on a schedule. 2. Fetches fleet vessel telemetry and AIS data from a configured HTTP API. 3. Retrieves weather forecast and port congestion context for each vessel/route from a second HTTP API. 4. Uses OpenAI to analyze telemetry against historical baselines and classify any operational anomalies with severity and confidence. 5. Uses OpenAI to aggregate anomaly, weather, and port context into risk factors, urgency, and an action category. 6. Uses OpenAI to simulate 2–3 routing and speed options, estimating cost, emissions, fuel, duration, and weather risk, and selects a recommended route. 7. Generates an executive briefing with compliance and master-authority notes, pauses for human approval via an n8n form, and then posts the decision and recommendation to a Slack channel. ## Setup 1. Add OpenAI API credentials for the three OpenAI chat model steps. 2. Configure HTTP Header Auth credentials and replace the placeholder URLs and query parameters for your AIS/telemetry API and your weather/port API. 3. Ensure the upstream APIs return the fields referenced in the prompts (for example position, speed, fuel consumption, historical baselines, forecast, and port congestion). 4. Connect a Slack OAuth2 credential and select the target channel for posting the approved briefing. 5. Test the approval form step in n8n and confirm who will receive and complete approvals before enabling the workflow.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Review n8n workflows from Slack with Claude Opus and GitHub skills

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Quick overview

How it works

Setup

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Slack: @mention or DM

Block 2 - Keep mentions and DMs

Block 3 - Add Eyes Reaction

Block 4 - Parse URL

Block 5 - Valid URL?

Block 6 - Get Top-Level Workflow

Block 7 - Remove Reaction (Bad URL)

Block 8 - Post Error: Bad URL

Block 9 - Remove Reaction (Fetch Failed)

Block 10 - Post Error: Fetch Failed

Block 11 - Fetch Review Checklist

Block 12 - Remove Reaction (Checklist Failed)

Block 13 - Post Error: Checklist Failed

Block 14 - Extract Subworkflow IDs

Block 15 - Split Out Subworkflow IDs

Block 16 - Get Each Subworkflow

Block 17 - Aggregate Subworkflows

Block 18 - Combine Branches

Block 19 - Empty Subworkflows

Block 20 - Build Agent Payload

Block 21 - Reviewer Agent

Block 22 - Get Skill File

Block 23 - Block Kit Output Parser

Block 24 - Remove Reaction (Agent Failed)

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions