Generate Azure VM timeline reports with Google Gemini AI chat assistant
Needs changesWhat this workflow does
This AI workflow has 11 nodes and runs when a chat message arrives. Along the way it connects HTTP Request and Google Gemini Chat Model.
How it runs
Trigger: When a chat message arrives.
- Set Common Variables (Edit Fields (Set)): sets 1 field: azure_subscription_id
- AI Agent: runs an AI agent, with model: Google Gemini Chat Model; 6 tools (Get VM Events, Get Current Date, Get VM Information, Get VM Instance View…); memory: Simple Memory
Services it uses
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- AI Agent v1 (old agent modes) in AI Agent (v1.8): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
- HTTP Request Tool (legacy) in Get VM Performance Stats, Get Azure Resource Groups, Get VM Information…: replace with HTTP Request node connected to the AI Agent's Tool input.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) AI Agent (v1.8) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
| HTTP Request Tool (legacy) Get VM Performance Stats, Get Azure Resource Groups, Get VM Information, Get VM Events, Get VM Instance View | HTTP Request node connected to the AI Agent's Tool input |
Nodes used (7)
- AI Agent
@n8n/n8n-nodes-langchain.agent - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request Tool
@n8n/n8n-nodes-langchain.toolHttpRequest - Chat Trigger
@n8n/n8n-nodes-langchain.chatTrigger - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Simple Memory
@n8n/n8n-nodes-langchain.memoryBufferWindow - Code Tool
@n8n/n8n-nodes-langchain.toolCode
From the author
An AI-powered chat assistant that analyzes Azure virtual machine activity and generates detailed timeline reports showing VM state changes, performance metrics, and operational events over time. How It Works The workflow starts with a chat trigger that…