Back to Catalog

Proxmox AI agent with n8n and generative AI integration

Amjid AliAmjid Ali
72116 views
2/3/2026
Official Page

Proxmox AI Agent with n8n and Generative AI Integration

This template automates IT operations on a Proxmox Virtual Environment (VE) using an AI-powered conversational agent built with n8n. By integrating Proxmox APIs and generative AI models (e.g., Google Gemini), the workflow converts natural language commands into API calls, enabling seamless management of your Proxmox nodes, VMs, and clusters. Buy My Book:
Mastering n8n on Amazon

Full Courses & Tutorials:
http://lms.syncbricks.com

Watch Video on Youtube

How It Works

  1. Trigger Mechanism

    • The workflow can be triggered through multiple channels like chat (Telegram, email, or n8n's built-in chat).
    • Interact with the AI agent conversationally.
  2. AI-Powered Parsing

    • A connected AI model (Google Gemini or other compatible models like OpenAI or Claude) processes your natural language input to determine the required Proxmox API operation.
  3. API Call Generation

    • The AI parses the input and generates structured JSON output, which includes:
      • response_type: The HTTP method (GET, POST, PUT, DELETE).
      • url: The Proxmox API endpoint to execute.
      • details: Any required payload parameters for the API call.
  4. Proxmox API Execution

    • The structured output is used to make HTTP requests to the Proxmox VE API. The workflow supports various operations, such as:
      • Retrieving cluster or node information.
      • Creating, deleting, starting, or stopping VMs.
      • Migrating VMs between nodes.
      • Updating or resizing VM configurations.
  5. Response Formatting

    • The workflow formats API responses into a user-friendly summary. For example:
      • Success messages for operations (e.g., "VM started successfully").
      • Error messages with missing parameter details.
  6. Extensibility

    • You can enhance the workflow by connecting additional triggers, external services, or AI models. It supports:
      • Telegram/Slack integration for real-time notifications.
      • Backup and restore workflows.
      • Cloud monitoring extensions.

Key Features

  • Multi-Channel Input: Use chat, email, or custom triggers to communicate with the AI agent.
  • Low-Code Automation: Easily customize the workflow to suit your Proxmox environment.
  • Generative AI Integration: Supports advanced AI models for precise command interpretation.
  • Proxmox API Compatibility: Fully adheres to Proxmox API specifications for secure and reliable operations.
  • Error Handling: Detects and informs you of missing or invalid parameters in your requests.

Example Use Cases

  1. Create a Virtual Machine

    • Input: "Create a VM with 4 cores, 8GB RAM, and 50GB disk on psb1."
    • Action: Sends a POST request to Proxmox to create the VM with specified configurations.
  2. Start a VM

    • Input: "Start VM 105 on node psb2."
    • Action: Executes a POST request to start the specified VM.
  3. Retrieve Node Details

    • Input: "Show the memory usage of psb3."
    • Action: Sends a GET request and returns the node's resource utilization.
  4. Migrate a VM

    • Input: "Migrate VM 202 from psb1 to psb3."
    • Action: Executes a POST request to move the VM with optional online migration.

Pre-Requisites

  1. Proxmox API Configuration

    • Enable the Proxmox API and generate API keys in the Proxmox Data Center.
    • Use the Authorization header with the format:
      PVEAPIToken=<user>@<realm>!<token-id>=<token-value>
  2. n8n Setup

    • Add Proxmox API credentials in n8n using Header Auth.
    • Connect a generative AI model (e.g., Google Gemini) via the relevant credential type.
  3. Access the Workflow

    • Import this template into your n8n instance.
    • Replace placeholder credentials with your Proxmox and AI service details.

Additional Notes

  • This template is designed for Proxmox 7.x and above.
  • For advanced features like backup, VM snapshots, and detailed node monitoring, you can extend this workflow.
  • Always test with a non-production Proxmox environment before deploying in live systems.

Start with n8n

Learn n8n with Amjid

Get n8n Book

What is Proxmox

# Proxmox AI Agent with n8n and Generative AI Integration

This n8n workflow demonstrates how to create an AI agent that can interact with a Proxmox server, potentially through an HTTP API, and respond to user queries received via Telegram or Gmail. It leverages Langchain AI agents for intelligent decision-making and action execution.

## What it does

This workflow orchestrates an AI agent to perform actions based on incoming messages:

1.  **Receives Input**: It can be triggered by new messages from either:
    *   **Telegram**: Listens for incoming chat messages.
    *   **Gmail**: Monitors for new emails.
    *   **Webhook**: Can also be triggered by a generic HTTP POST request.
2.  **Initial Message Processing**: A `Code` node processes the incoming message, likely extracting the relevant text for the AI agent.
3.  **AI Agent Decision Making**: The core `AI Agent` node, powered by a `Google Gemini Chat Model`, analyzes the user's request. It's configured with:
    *   **Structured Output Parser**: To ensure the AI's output adheres to a predefined JSON structure.
    *   **Auto-fixing Output Parser**: To attempt to correct any malformed output from the AI, ensuring robustness.
    *   **HTTP Request Tool**: The AI agent has access to an `HTTP Request Tool`, allowing it to make API calls to external services (e.g., a Proxmox API).
4.  **Conditional Logic**: An `If` node checks if the AI agent's response contains a specific keyword or condition (e.g., "Proxmox").
5.  **Proxmox Interaction (Conditional)**:
    *   If the condition is met, the `HTTP Request` node is executed, presumably interacting with the Proxmox API based on the AI's decision.
    *   If the condition is not met, the workflow proceeds without Proxmox interaction.
6.  **Response Merging**: A `Merge` node combines the outputs from the conditional branches, ensuring a unified flow.
7.  **Final Output**: The workflow ends, ready to process the next incoming message.

## Prerequisites/Requirements

To use this workflow, you will need:

*   **n8n Instance**: A running n8n instance.
*   **Telegram Account & Bot Token**: For the Telegram Trigger. You'll need to create a Telegram Bot and obtain its API token.
*   **Gmail Account**: For the Gmail Trigger. You'll need to configure Gmail credentials in n8n.
*   **Google Gemini API Key**: For the `Google Gemini Chat Model`.
*   **Proxmox Server**: Access to a Proxmox server and its API documentation if you intend to use the `HTTP Request` node for Proxmox interaction.
*   **API Endpoint for Proxmox (Optional)**: If the `HTTP Request` node is indeed used for Proxmox, you'll need the relevant API endpoint and authentication details.

## Setup/Usage

1.  **Import the Workflow**:
    *   Download the provided JSON file.
    *   In your n8n instance, go to "Workflows" and click "New".
    *   Click the "Import from JSON" button and paste the workflow JSON or upload the file.
2.  **Configure Credentials**:
    *   **Telegram Trigger**: Configure your Telegram Bot API credentials.
    *   **Gmail Trigger**: Configure your Google OAuth2 credentials for Gmail.
    *   **Google Gemini Chat Model**: Configure your Google Gemini API key.
3.  **Configure AI Agent**:
    *   Open the `AI Agent` node and ensure the `Google Gemini Chat Model` is correctly linked and configured with your API key.
    *   Review the `Structured Output Parser` and `Auto-fixing Output Parser` settings.
    *   Examine the `HTTP Request Tool` within the AI Agent to understand how it's intended to interact with external APIs. You might need to define its capabilities (e.g., "tool to manage Proxmox VMs").
4.  **Configure HTTP Request Node (Proxmox Interaction)**:
    *   Open the `HTTP Request` node (node ID 19).
    *   Set the `URL`, `Method`, `Headers`, and `Body` according to your Proxmox API documentation. This node will be executed if the AI agent determines a Proxmox action is needed.
5.  **Configure If Node**:
    *   Review the conditions in the `If` node (node ID 20) to ensure it correctly identifies when Proxmox-related actions should be taken based on the AI agent's output.
6.  **Activate the Workflow**: Once all configurations are complete, activate the workflow.

Now, when a message is received via Telegram, Gmail, or the Webhook, the AI agent will process it, decide on an appropriate action (potentially interacting with Proxmox), and follow the defined logic.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch πŸ”— LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

AI-powered code review with linting, red-marked corrections in Google Sheets & Slack

Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting β€” all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow β€” reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n β€” combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.

higashiyama By higashiyama
90

πŸŽ“ How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits βœ… Full Automation: Eliminates manual reading and data entry from incoming emails. βœ… Multi-Source Integration: Handles data from different email providers seamlessly. βœ… AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. βœ… Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. βœ… Time Efficiency: Processes emails in real time, improving productivity and response speed. *βœ… Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616