Quick overview
This workflow collects a stack choice and notification email via a form, lets you pick a Hostinger VPS, deploys the selected curated app stack as separate Docker Compose projects using the Hostinger API, and emails a per-app deployment summary with ports, container status, and generated credentials.
How it works
- Receives a form submission with the selected stack (Developer, Hobbyist, Freelancer, or AI/LLM) and a notification email address.
- Uses the Hostinger API to list available VPS instances and presents a second form to select the target virtual machine.
- Expands the chosen stack into one item per app by generating Docker Compose content and creating random values for any required secrets.
- Creates a Docker Compose project for each app on the selected Hostinger VPS via the Hostinger API.
- Waits briefly, polls the Hostinger action status for each deployment, and branches based on whether the action completes successfully.
- On success, lists the project’s containers and formats a status block including ports, container states, and any generated credentials, and on failure, fetches recent Docker project logs and formats an error block.
- Aggregates all per-app blocks into a single summary and sends the deployment report to the provided email address via SMTP.
Setup
- Self-host n8n and install the community node
n8n-nodes-hostinger-api (Settings → Community Nodes).
- Create and connect a Hostinger API credential with access to your VPS account.
- Configure an SMTP email credential for the email-sending step, and set valid From/To behavior (the template uses the submitted notification email for both).
- Ensure the target VPS has Docker available and that deploying these containers and exposing the listed ports fits your security requirements.
Requirements
- Self-hosted n8n
- Hostinger VPS + API Key
- SMTP Mailbox