Skip to main content

Monitor asset health and predict maintenance with Anthropic Claude and Slack

Workflow preview

Workflow preview
100%
Monitor asset health and predict maintenance with Anthropic Claude and Slack preview
Open on n8n.io

1. Workflow Overview

How It Works This workflow automates industrial asset health monitoring and predictive maintenance using Anthropic Claude across coordinated specialist agents. It targets facility managers, mainten...

Best for

  • Engineering automation workflows
  • AI RAG automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.scheduletrigger, n8n-nodes-base.set, n8n-nodes-base.code, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.agenttool, @n8n/n8n-nodes-langchain.lmchatanthropic, @n8n/n8n-nodes-langchain.outputparserstructured, @n8n/n8n-nodes-langchain.mcpclienttool

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Cheng Siong Chin.

Original n8n.io source

1.1 Workflow description

Title
Monitor asset health and predict maintenance with Anthropic Claude and Slack
Workflow name
Monitor asset health and predict maintenance with Anthropic Claude and Slack

How It Works

This workflow automates industrial asset health monitoring and predictive maintenance using Anthropic Claude across coordinated specialist agents. It targets facility managers, maintenance engineers, and operations teams in manufacturing, energy, and infrastructure sectors where reactive maintenance leads to costly unplanned downtime and asset failures. On schedule, the system ingests asset health data and routes it through a Performance Evaluation Agent that coordinates three specialist agents: Maintenance Scheduling, Parts Readiness, and Lifecycle Reporting. An MCP External Data Tool enriches analysis with real-time contextual data. Results are risk-routed—Critical assets trigger immediate Slack alerts, High-risk assets escalate via email reports, and Routine cases are logged for scheduled maintenance. All paths merge into a unified maintenance log, giving operations teams proactive, audit-ready asset intelligence before failures occur.

Setup Steps

  1. Import workflow JSON into your n8n instance.
  2. Add Anthropic API credentials.
  3. Set Schedule Trigger frequency aligned to your asset monitoring cycle.
  4. Update Workflow Configuration node with asset thresholds.
  5. Configure MCP External Data Tool with your external data source endpoint and authentication.
  6. Add Slack credentials and set the target channel in the Notify Critical Alert node.
  7. Set Gmail/SMTP credentials for the Email Escalation Report node.

Prerequisites

n8n (cloud or self-hosted), Anthropic API key (Claude), Slack workspace with bot token

Use Cases

Facility managers automating condition-based maintenance scheduling across multiple assets

Customization

Replace Anthropic Claude with OpenAI GPT-4 or NVIDIA NIM in any agent node

Benefits

Shifts maintenance from reactive to predictive, reducing unplanned downtime significantly

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 - Schedule Asset Health Check

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

Block 2 - Workflow Configuration

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

Block 3 - Generate Asset Health Data

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

Block 4 - Performance Evaluation Agent

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

Block 5 - Maintenance Scheduling Agent Tool

Type / Role
@n8n/n8n-nodes-langchain.agentTool - agentTool
Config choices
Version 3

Block 6 - Parts Readiness Agent Tool

Type / Role
@n8n/n8n-nodes-langchain.agentTool - agentTool
Config choices
Version 3

Block 7 - Lifecycle Reporting Agent Tool

Type / Role
@n8n/n8n-nodes-langchain.agentTool - agentTool
Config choices
Version 3

Block 8 - Anthropic Model - Performance Agent

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

Block 9 - Anthropic Model - Maintenance Tool

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

Block 10 - Anthropic Model - Parts Tool

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

Block 11 - Anthropic Model - Lifecycle Tool

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

Block 12 - Performance Analysis Output Parser

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

Block 13 - Maintenance Scheduling Output Parser

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

Block 14 - Parts Readiness Output Parser

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

Block 15 - Lifecycle Reporting Output Parser

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

Block 16 - MCP External Data Tool

Type / Role
@n8n/n8n-nodes-langchain.mcpClientTool - mcpClientTool
Config choices
Version 1.2

Block 17 - Route by Risk Level

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

Block 18 - Notify Critical Alert

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

Block 19 - Email Escalation Report

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 20 - Log Routine Maintenance

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

Block 21 - Merge All Paths

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

Block 22 - Sticky Note

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

Block 23 - Sticky Note1

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

Block 24 - Sticky Note2

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

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

3. Summary Table

Workflow Monitor asset health and predict maintenance with Anthropic Claude and Slack
Complexity advanced
Nodes 27
Categories Engineering, AI RAG
Author Cheng Siong Chin
Published 22 Feb 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/13595/13595.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 Monitor asset health and predict maintenance with Anthropic Claude and Slack do?

How It Works This workflow automates industrial asset health monitoring and predictive maintenance using Anthropic Claude across coordinated specialist agents. It targets facility managers, mainten...

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 RAG use case.