You can automate Hostinger VPS checks by calling the Hostinger API from an n8n HTTP Request node. Authenticate with a Hostinger API token saved as a Bearer credential, put a schedule trigger in front of the node, and route the JSON response through a condition to Slack, Google Sheets or another destination. Hostinger’s tutorial of September 15, 2026 shows this pattern for server-state alerts, backup logging and malware-scan reporting.
What you can automate
Hostinger’s examples are monitoring and reporting workflows, not a promise that every server operation is exposed through every endpoint. Its API overview mentions tasks such as retrieving VPS metrics and restarting a server. Check the current API reference for the exact endpoint, parameters and requirements before building each workflow.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
ZOERAX 100-Pack M6 x 16mm Rack Mount Cage Nuts, Screws and Washers | $23.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
| Workflow | What it queries | Condition | Destination in Hostinger’s example |
|---|---|---|---|
| VPS state alert | The virtual-machine endpoint for your VPS ID | Returned state is one you treat as a problem (the sample includes stopped, destroyed and suspended) |
Slack notification |
| Backup logging | The backups endpoint, with the documented page parameter | None needed; record the latest backup date | Google Sheets |
| Malware-scan reporting | The Monarx endpoint | Malicious-file count is above your threshold | Notification to an operator |
Where to run n8n
Run n8n somewhere other than the VPS it watches. Hostinger’s tutorial warns: “Avoid hosting your n8n instance on the same VPS you want to monitor because your workflow will also fail if the server experiences downtime.” A state alert is useless if it dies with the server it reports on.
Hostinger’s Help Center also documents an Ubuntu 24.04 VPS template with n8n preinstalled in Docker. It is a convenient way to deploy n8n, but you don’t need it to call the API. If you use it, put it on a separate VPS from the ones you monitor.
#1 Best Overall
- Wide Compatibility & Versatile Use: ZOERAX M6 rack mount screw kit is ideal for installing server racks, network cabinets, rack shelves, patch panels, A/V equipment, and more. Designed for standard square-hole racks and cabinets, these M6 cage nuts and screws ensure a secure fit for most 19-inch rack systems used in data centers, offices, and home labs
- Heavy-Duty Carbon Steel Construction: Made from premium carbon steel, these M6 cage nuts and screws deliver high strength and long-lasting durability. The material provides excellent resistance to rust, corrosion, and oxidation, performing reliably in demanding environments such as high humidity, temperature fluctuations, and long-term rack installations
- Precision Metric Standard M6: Manufactured to strict metric standards, each M6 screw and cage nut features precise dimensions with minimal tolerance. Clean, sharp threads without burrs allow smooth installation without stripping or slipping. The deep Phillips head design ensures better torque control and faster, more efficient mounting
- Safe, Reliable & Eco-Conscious Materials: ZOERAX uses non-toxic, environmentally friendly carbon steel materials to ensure safe handling and use. Heat-treated for optimal hardness, ductility, and impact resistance, these rack screws and cage nuts offer dependable performance while meeting safety and quality expectations for professional installations
- Complete Mounting Kit with Washers: This essential M6 rack hardware kit includes screws, cage nuts, and heavy-duty washers. The included washers help distribute pressure evenly and reduce scratches or marks on rack rails and equipment, providing a cleaner, more secure installation right out of the box
How to connect n8n to the Hostinger API
1. Create an API token
Generate a token in the Hostinger dashboard; the Help Center describes this under account settings. Save it as an n8n credential. Do not paste it into the endpoint or the workflow text, where it would be exposed in exports and shared workflows.
2. Make a first request
- Add an HTTP Request node.
- Enter the endpoint. Hostinger’s example is
https://developers.hostinger.com/api/vps/v1/virtual-machines/123456, where123456is a placeholder for your real VPS ID. - Choose generic Bearer authentication and select the credential holding your token.
- Run the node and inspect the JSON before adding any logic. You need to see the actual field names to write your conditions.
If the request fails, Hostinger’s checklist is: confirm the VPS ID, the credential configuration, that the token is valid, and that the endpoint is spelled correctly with any required parameters.
3. Add a trigger, a filter and an action
- Add a Schedule Trigger and connect it to the HTTP Request node. Pick an interval that matches how fast you need to know.
- Add a condition node (such as If) that tests the field you care about, for example the
statevalue. - Connect the matching branch to a Slack, spreadsheet or other node.
Decide up front which states count as an alert. Hostinger’s sample treats stopped, destroyed and suspended as concerning, but you may want a narrower or wider list.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choosing between the HTTP Request node and the Hostinger API node
Hostinger documents two routes. The HTTP Request node works in any n8n deployment and is what the tutorial uses. A Hostinger API community node, n8n-nodes-hostinger-api, is installed and given the same kind of API token as its credential. Hostinger’s Help Center states that community nodes are available only in self-hosted n8n.
Hostinger’s December 22, 2025 announcement also describes an official Hostinger API n8n node, with automation examples covering servers, Docker containers, backups and domains. Confirm in your n8n instance that the node is available and supports the endpoint you need. If it doesn’t, the HTTP Request node still works.
Quick Recap
| Factor | HTTP Request node | Hostinger API node |
|---|---|---|
| Works on n8n deployments without community nodes | Yes | Community node: self-hosted only, per Hostinger’s Help Center |
| Endpoint coverage | Any endpoint in the API reference | Depends on the node version; check before relying on it |
| Setup | You write the URL and parameters | Install the node and add the token credential |
Limits worth knowing
- Hostinger has not published performance or reliability figures for this setup, so avoid claiming any time-saving or error-reduction percentage.
- API screens, node availability and template details change. Verify against the current Hostinger API documentation and your n8n interface before you rely on a given step.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
