Porxmox Custom AI Agent
Configured with Agent, Chat Trigger, Gmail Trigger, HTTP Request, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Transform
- AI & models
- Trigger
- Code
- Routing
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| HTTP Request1 | Web / API | HTTP Request | =POST |
| Proxmox API Documentation | Web / API | Tool Http Request | See node parameters |
| Auto-fixing Output Parser | Transform | Output Parser Autofixing | See node parameters |
| Google Gemini Chat Model1 | AI & models | LM Chat Google Gemini | See node parameters |
| Structured Output Parser | Transform | Output Parser Structured | See node parameters |
| Proxmox | Web / API | Tool Http Request | See node parameters |
| HTTP Request | Web / API | HTTP Request | =GET |
| Google Gemini Chat Model2 | AI & models | LM Chat Google Gemini | See node parameters |
| When chat message received | Trigger | Chat Trigger | See node parameters |
| Telegram Trigger | Trigger | Telegram Trigger | See node parameters |
| Gmail Trigger | Trigger | Gmail Trigger | See node parameters |
| Webhook | Trigger | Webhook | See node parameters |
| Proxmox API Wiki | Web / API | Tool Http Request | See node parameters |
| Structure Response | Code | Code | See node parameters |
| Structgure Response from Proxmox | Code | Code | See node parameters |
| Format Response and Hide Sensitive Data | Code | Code | See node parameters |
| If | Routing | If | See node parameters |
| HTTP Request2 | Web / API | HTTP Request | =POST |
| Merge | Transform | Merge | See node parameters |
| HTTP Request3 | Web / API | HTTP Request | DELETE |
| Google Gemini Chat Model | AI & models | LM Chat Google Gemini | See node parameters |
| AI Agent1 | AI & models | Agent | See node parameters |
| If1 | Routing | If | See node parameters |
| HTTP Request4 | Web / API | HTTP Request | DELETE |
| Merge1 | Transform | Merge | See node parameters |
| AI Agent | AI & models | Agent | See node parameters |
| Switch | Routing | Switch | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
gmailOAuth2googlePalmApihttpHeaderAuthtelegramApi
Workflow notes
API Key for Proxmox
API Key for Proxmox
** Create Credentails *** ensure to create credentials in Proxmox Data Center as API Key and then create credentails. ** Add Credentials to n8n ** Click on Credentails, add new Credentails and Chose Header Auth ** In Header Auth Below will be used Name : Authorization Value : PVEAPIToken=@!=
Suppose my token id is n8n and key is 1234 so value will be as below
Value : PVEAPIToken=root@pam!n8n=1234
Trigger
Trigger
You can use any trigger as input, a chat, telegram, email etc
Porxmox Custom AI Agent
Porxmox Custom AI Agent
It uses the intelligence provided to it including the Proxmox API Wiki, Proxmox Cluster Linked and Proxmox API Documentation.
The AI Model connected with this is Gemini, you can connect any AI Model by Ollama, OpenAI, Claude etc.
Output Parser is used to ensure the fixed output structure that can be used for API URL
HTTP methods
HTTP methods
GET Retrieve resources Fetch VM status, list nodes, get logs.
POST Create or trigger actions Start/stop VMs, create backups.
PUT Update/replace entire resource configuration Modify VM configurations.
DELETE Delete resources Remove VMs, delete users, remove files.
OPTIONS Fetch supported methods for an endpoint Check available operations for an API.
PATCH Apply partial updates Update specific fields in VM settings.
Porxmox Custom AI Agent (Get)
Porxmox Custom AI Agent (Get)
This agent will convert the response from proxmox to meaningful explanation
Created or triggered an action on the server.
Created or triggered an action on the server.
Response will come back here
Trigger
Trigger
You can use any trigger as input, a chat, telegram, email etc
You can think of any input, even it could be from your cloud platform, your own Web Applicaiton, etc.
Possibilities are limitless.
Chat is shown just as example.
Developed by Amjid Ali
Developed by Amjid Ali
Thank you for using this workflow template. It has taken me countless hours of hard work, research, and dedication to develop, and I sincerely hope it adds value to your work.
If you find this template helpful, I kindly ask you to consider supporting my efforts. Your support will help me continue improving and creating more valuable resources.
You can contribute via PayPal here:
http://paypal.me/pmptraining
Additionally, when sharing this template, I would greatly appreciate it if you include my original information to ensure proper credit is given.
Thank you for your generosity and support! Email : user@example.com https://linkedin.com/in/amjidali https://syncbricks.com https://youtube.com/@syncbricks
Porxmox Custom AI Agent
Porxmox Custom AI Agent
Purpose and structure
This folder contains the Porxmox Custom AI Agent workflow. Its executable nodes use agent, chatTrigger, code, gmailTrigger, httpRequest, if, lmChatGoogleGemini, merge, outputParserAutofixing, outputParserStructured, switch, telegramTrigger, toolHttpRequest, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When chat message received, Telegram Trigger, Gmail Trigger, Webhook
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/0690_Telegram_Webhook_Send_Webhook.json MIT; preserve source notices.