Skip to main content

Amazon CloudWatch Application Insights API with 27 operations

Workflow preview

Workflow preview
100%
Amazon CloudWatch Application Insights API with 27 operations preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Complete MCP server exposing 27 Amazon CloudWatch Application Insights API operations to AI agents. Quick Setup Need help? Want access to more workflows and even live Q&A sessions with a top veri...

Best for

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

Tools used

n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.mcptrigger, n8n-nodes-base.httprequesttool

Source and attribution

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

Original n8n.io source

1.1 Workflow description

Title
Amazon CloudWatch Application Insights API with 27 operations
Workflow name
Amazon CloudWatch Application Insights API with 27 operations

Complete MCP server exposing 27 Amazon CloudWatch Application Insights API operations to AI agents.

⚑ Quick Setup

Need help? Want access to more workflows and even live Q&A sessions with a top verified n8n creator.. All 100% free?

Join the community

  1. Import this workflow into your n8n instance
  2. Credentials Add Amazon CloudWatch Application Insights credentials
  3. Activate the workflow to start your MCP server
  4. Copy the webhook URL from the MCP trigger node
  5. Connect AI agents using the MCP URL

πŸ”§ How it Works

This workflow converts the Amazon CloudWatch Application Insights API into an MCP-compatible interface for AI agents.

β€’ MCP Trigger: Serves as your server endpoint for AI agent requests β€’ HTTP Request Nodes: Handle API calls to http://applicationinsights.{region}.amazonaws.com β€’ AI Expressions: Automatically populate parameters via $fromAI() placeholders β€’ Native Integration: Returns responses directly to the AI agent

πŸ“‹ Available Operations (27 total)

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Createapplication (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.CreateApplication: Adds an application that is created from a resource group.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Createcomponent (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.CreateComponent: Creates a custom component by grouping similar standalone instances to monitor.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Createlogpattern (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.CreateLogPattern: Adds an log pattern to a LogPatternSet.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Deleteapplication (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DeleteApplication: Removes the specified application from monitoring. Does not delete the application.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Deletecomponent (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DeleteComponent: Ungroups a custom component. When you ungroup custom components, all applicable monitors that are set up for the component are removed and the instances revert to their standalone status.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Deletelogpattern (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DeleteLogPattern: Removes the specified log pattern from a LogPatternSet.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Describeapplication (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DescribeApplication: Describes the application.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Describecomponent (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DescribeComponent: Describes a component and lists the resources that are grouped together in a component.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Describecomponentconfiguration (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DescribeComponentConfiguration: Describes the monitoring configuration of the component.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Describecomponentconfigurationrecommendation (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DescribeComponentConfigurationRecommendation: Describes the recommended monitoring configuration of the component.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Describelogpattern (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DescribeLogPattern: Describe a specific log pattern from a LogPatternSet.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Describeobservation (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DescribeObservation: Describes an anomaly or error with the application.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Describeproblem (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DescribeProblem: Describes an application problem.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Describeproblemobservations (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.DescribeProblemObservations: Describes the anomalies or errors associated with the problem.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Listapplications (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.ListApplications: Lists the IDs of the applications that you are monitoring.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Listcomponents (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.ListComponents: Lists the auto-grouped, standalone, and custom components of the application.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Listconfigurationhistory (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.ListConfigurationHistory:

Lists the INFO, WARN, and ERROR events for periodic configuration updates performed by Application Insights. Examples of events represented are:

  • INFO: creating a new alarm or updating an alarm threshold.

  • WARN: alarm not created due to insufficient data points used to predict thresholds.

  • ERROR: alarm not created due to permission errors or exceeding quotas.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Listlogpatternsets (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.ListLogPatternSets: Lists the log pattern sets in the specific application.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Listlogpatterns (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.ListLogPatterns: Lists the log patterns in the specific log LogPatternSet.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Listproblems (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.ListProblems: Lists the problems with your application.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Listtagsforresource (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.ListTagsForResource: Retrieve a list of the tags (keys and values) that are associated with a specified application. A tag is a label that you optionally define and associate with an application. Each tag consists of a required tag key and an optional associated tag value. A tag key is a general label that acts as a category for more specific tag values. A tag value acts as a descriptor within a tag key.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Tagresource (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.TagResource:

Add one or more tags (keys and values) to a specified application. A tag is a label that you optionally define and associate with an application. Tags can help you categorize and manage application in different ways, such as by purpose, owner, environment, or other criteria.

Each tag consists of a required tag key and an associated tag value, both of which you define. A tag key is a general label that acts as a category for more specific tag values. A tag value acts as a descriptor within a tag key.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Untagresource (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.UntagResource: Remove one or more tags (keys and values) from a specified application.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Updateapplication (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.UpdateApplication: Updates the application.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Updatecomponent (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.UpdateComponent: Updates the custom component name and/or the list of resources that make up the component.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Updatecomponentconfiguration (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.UpdateComponentConfiguration: Updates the monitoring configurations for the component. The configuration input parameter is an escaped JSON of the configuration and should match the schema of what is returned by DescribeComponentConfigurationRecommendation.

πŸ”§ #X-Amz-Target=Ec2Windowsbarleyservice.Updatelogpattern (1 endpoints)

β€’ POST /#X-Amz-Target=EC2WindowsBarleyService.UpdateLogPattern: Adds a log pattern to a LogPatternSet.

πŸ€– AI Integration

Parameter Handling: AI agents automatically provide values for: β€’ Path parameters and identifiers β€’ Query parameters and filters β€’ Request body data β€’ Headers and authentication

Response Format: Native Amazon CloudWatch Application Insights API responses with full data structure

Error Handling: Built-in n8n HTTP request error management

πŸ’‘ Usage Examples

Connect this MCP server to any AI agent or workflow:

β€’ Claude Desktop: Add MCP server URL to configuration β€’ Cursor: Add MCP server SSE URL to configuration β€’ Custom AI Apps: Use MCP URL as tool endpoint β€’ API Integration: Direct HTTP calls to MCP endpoints

✨ Benefits

β€’ Zero Setup: No parameter mapping or configuration needed β€’ AI-Ready: Built-in $fromAI() expressions for all parameters β€’ Production Ready: Native n8n HTTP request handling and logging β€’ Extensible: Easily modify or add custom logic

> πŸ†“ Free for community use! Ready to deploy in under 2 minutes.

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 - Setup Instructions

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

Block 2 - Workflow Overview

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

Block 3 - Amazon CloudWatch Application Insights MCP Server

Type / Role
@n8n/n8n-nodes-langchain.mcpTrigger - mcpTrigger
Config choices
Version 1

Block 4 - Adds an application that is created from a resourc

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

Block 5 - Grid Note 1

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

Block 6 - Creates a custom component by grouping similar sta

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

Block 7 - Grid Note 2

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

Block 8 - Adds an log pattern to a <code>LogPatternSet</code

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

Block 9 - Grid Note 3

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

Block 10 - Removes the specified application from monitoring.

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

Block 11 - Grid Note 4

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

Block 12 - Ungroups a custom component. When you ungroup cust

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

Block 13 - Grid Note 5

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

Block 14 - Removes the specified log pattern from a <code>Log

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

Block 15 - Grid Note 6

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

Block 16 - Describes the application.

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

Block 17 - Grid Note 7

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

Block 18 - Describes a component and lists the resources that

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

Block 19 - Grid Note 8

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

Block 20 - Describes the monitoring configuration of the comp

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

Block 21 - Grid Note 9

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

Block 22 - Describes the recommended monitoring configuration

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

Block 23 - Grid Note 10

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

Block 24 - Describe a specific log pattern from a <code>LogPa

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

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

3. Summary Table

Workflow Amazon CloudWatch Application Insights API with 27 operations
Complexity advanced
Nodes 57
Categories DevOps, AI RAG
Author David Ashby
Published 01 Jul 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/5498/5498.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 Amazon CloudWatch Application Insights API with 27 operations do?

Complete MCP server exposing 27 Amazon CloudWatch Application Insights API operations to AI agents. Quick Setup Need help? Want access to more workflows and even live Q&A sessions with a top veri...

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