Turn simple messages into real Proxmox actions. Teams can start, stop, change, and check virtual machines by sending a chat, an email, a Telegram message, or a webhook call. It helps IT staff handle requests faster and keeps work in one place.

Incoming text is parsed by a Gemini model that knows the Proxmox API docs and wiki. The model creates a clear plan with method, URL, and body. A structured parser locks the format so the API call is always valid. A switch then routes the call to the right HTTP method for GET, POST, PUT, PATCH, or DELETE. Responses are merged, explained in plain language, and cleaned to hide sensitive data.

Setup needs a Proxmox API token in a header, a Google Gemini key, and optional Telegram and Gmail accounts. Expect faster VM operations and fewer mistakes. Use this to spin up new VMs, change CPU or memory, trigger backups, or get logs without opening the Proxmox UI. It scales across many requests and works from multiple entry points.

• Multiple triggers accept input from chat, Telegram, Gmail, and webhook.
• Gemini model reads Proxmox docs and wiki to turn intent into API calls.
• Structured output parser enforces method, URL, and body schema.
• Switch and If nodes route to GET, POST, PUT, PATCH, or DELETE HTTP calls.
• HTTP header auth uses PVEAPIToken for secure Proxmox access.
• Allows self signed certificates for on prem Proxmox endpoints.
• Merges responses and explains results in plain language.
• Removes sensitive fields before returning the final output.

• Reduce manual VM tasks from 30 minutes to 2 minutes
• Automate up to 80 percent of routine Proxmox actions
• Cut API mistakes by 90 percent with structured output and auto fix
• Connect chat, email, and web apps into one control lane
• Handle many requests in parallel with smart routing and merge

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Proxmox, Google Gemini, Telegram, Gmail and Webhook.site. See the Tools Required section above for links to create accounts with these services.
3. Create a Proxmox API token in your Proxmox data center. Copy the token ID and secret value. You will use HTTP header auth with the name Authorization and value PVEAPIToken=user@realm!token-id=token-value.
4. In the n8n credentials manager, create a new HTTP Header Auth credential named Proxmox. Add the Authorization header with your PVEAPIToken value. Save it.
5. Open each HTTP Request node and select the Proxmox credential in the Credential to connect with dropdown. Keep Allow Unauthorized Certs enabled if your server uses a self signed certificate.
6. Set up Google Gemini: double click the Gemini nodes, choose Create new credential, then follow the on screen steps to add your Google API key. Save it.
7. Connect Telegram: open the Telegram Trigger, click Create new credential, paste your bot token from BotFather, and save. Enable the trigger to register the webhook.
8. Connect Gmail: open the Gmail Trigger node, click Create new credential, and complete the OAuth flow. Choose the mailbox and label or filter you want to watch.
9. Test webhooks: open the Webhook node, copy the Production URL, and send a sample POST from Webhook.site or your app to confirm receipt.
10. Update Proxmox base URLs if needed. The nodes use the api2 json pattern. Make sure the host and port match your cluster.
11. Send a simple request like list nodes or start VM 105 using chat, Telegram, Gmail, or webhook. Check that the Switch routes to the correct HTTP method and that a response returns.
12. If you see 401 errors, verify the Authorization header value. If you see certificate errors, keep Allow Unauthorized Certs on or install a valid certificate on the server.
13. Turn on the workflow and watch execution logs to confirm the response is parsed, explained, and cleaned before output.