n8n Hosting
Build advanced workflow automations with visual nodes, webhooks, code, and hundreds of integrations.
- One click deploy
- 1 GB RAM Memory needed
- 15 GB Disk Space Needed
- From 2 € Price
Official links
n8n’s official links and original website
n8n GitHub
Go to Repositoryn8n Website
More
Tech
- Docker image
- docker.n8n.io/n8nio/n8n:latest
- Default port
- 5678
- Database
- postgres
How n8n works
An n8n workflow is a connected graph of nodes. A trigger starts the workflow when an event, schedule, webhook, or manual action occurs, and later nodes retrieve data, transform it, make decisions, call services, or return a response. Credentials are stored in the instance so approved workflows can connect to external applications without placing secrets directly inside every step.
Each run creates an execution record that can help operators understand what happened and where a failure occurred. Workflows can branch, loop, call APIs, process files, or use code when a prebuilt action is not enough. The visual editor lowers the barrier to following the logic, but complex automations still need testing, error handling, and ownership.
Key n8n features
Built-in integration nodes cover many common services, while HTTP requests and webhooks connect systems that expose APIs. Expressions map data between steps, and code nodes provide a controlled escape hatch for transformations or business rules that are awkward to express visually.
Triggers can respond to incoming webhooks, schedules, or events from connected applications. Error workflows and execution history support investigation when an automation fails. Publishing separates an active production workflow from a draft being edited, which helps teams make changes deliberately.
n8n vs Zapier
n8n gives technical teams control over a self-hosted workflow engine, visual logic, data transformations, and custom code. Zapier is a hosted no-code automation platform with connections across thousands of applications, a guided interface, and ready-made workflow templates.
Zapier may suit teams that want the provider to operate the automation platform and supply a large catalogue of preconfigured connections. n8n is attractive when workflows need deeper branching, custom API work, code, or control of execution data.
Who uses n8n
Operations teams automate handoffs between forms, spreadsheets, ticketing tools, and messaging systems. Developers use webhooks and APIs to connect internal services, while sales and support teams can synchronise records or trigger notifications without building a full integration service from scratch.
n8n is most effective when each workflow has an owner, documented credentials, test data, and a failure plan. It is less appropriate for unattended critical processes when nobody is prepared to monitor executions or respond to changes in third-party APIs.
Self-hosting n8n: requirements and cost
Resource use depends on how many workflows run at once, how long they run, the size of their payloads, the number of nodes, and the amount of execution history retained. PostgreSQL stores workflow definitions, users, credential metadata, and execution records, so the complete stack needs more headroom than the application-only RAM figure.
The software itself is free to run, and AvaHost maps n8n to Plan 2 at €5 for the application and PostgreSQL stack. One-click deployment provisions n8n and PostgreSQL, but the database remains unmanaged by AvaHost. AvaHost includes automatic n8n updates, scheduled backups, custom-domain support, and automated HTTPS. Busy webhook endpoints, large files, or concurrent long-running workflows may require a larger plan.
F.A.Q
The mapped minimum for n8n is Plan 2 at €5 for the application and PostgreSQL stack. That plan can suit a small number of light workflows, but concurrent executions, large payloads, retained history, long waits, and code steps can increase demand. External API charges or subscriptions remain separate from the AvaHost plan.
The one-click stack provisions PostgreSQL and connects it to n8n automatically. Workflow definitions, users, credential metadata, and execution records depend on that database. PostgreSQL is included but remains unmanaged by AvaHost, so administrators should consider persistent application data and database records together when reviewing changes or recovery requirements.
A custom domain with automated HTTPS can give production webhooks and the editor a stable public address. External services save webhook URLs, so the domain should be final before critical integrations are activated. Each connected service should be retested after a URL change to verify triggers, callbacks, authentication, and returned responses.
AvaHost applies n8n updates automatically while persistent application data and PostgreSQL remain attached to the installation. Scheduled backups are included. Workflow owners should still review release notes for changed nodes, credentials, or execution behaviour and test business-critical automations after major updates are applied.