n8n

What you can use it for

• Connect APIs and automate recurring operational tasks.
• Build webhook-triggered workflows for your applications.

Choose the right configuration

The standard template has n8n and a task-runner service, with SQLite data in /home/node/.n8n. A task runner is not a queue worker. Compare the PostgreSQL variant when you want a separate database; review the queue variant's Redis, worker and compatibility requirements before switching.

What this template creates

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

1. Select Configure deployment and sign in or create an account.
2. Choose a new or existing project and select an available region.
3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Check your deployment

After creating the owner account, run a small workflow and trigger a webhook through the public URL. If you use a Code node, test it too and inspect both n8n and task-runner logs. Reopen a saved workflow after a controlled restart and confirm its credentials still work before connecting important automations.

Operating this application

• Complete n8n's initial account setup after the service becomes reachable. Verify webhook URLs against the domain you actually use.
• Preserve workflow data and encryption settings across restarts and updates; losing an encryption key can make stored credentials unusable.
• Test a representative workflow after deployment and before upgrading. Model and third-party API charges are separate from hosting.

Hosting costs

Budget for both n8n and its task runner. Execution frequency, concurrent workflows and retained execution data affect resource needs; database and queue variants add services. Third-party API charges remain separate.

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-15

Upstream documentation ↗Template source and license ↗