Examples

How to deploy n8n on Zenifra

n8n can be deployed on Zenifra as an HTTP project from the official image. This guide shows the recommended configuration, the required variables, and how to validate the result.

Prerequisites

  • A verified account and access to the console.
  • Permission to create projects in the organization (project.create).
  • Credit or a saved card for the selected plan; see Payment models.

Quick option: template

n8n is in the public Templates catalog. Use Deploy to create the application with the recommended configuration, or Customize to review plan, storage, and variables and optionally create a database with it before confirming. The steps below show a manual configuration from the official image.

Step 1: create the HTTP project

In the console, click + Create Project, choose HTTP, and fill in:

FieldValue
Project sourceOCI Image
Imagedocker.io/n8nio/n8n:2.5.2
RegistryPublic, no authentication
PlanPremium (1 vCPU and 1 GB RAM) handles most workflows. For high execution volume, use Premium Plus or higher.
Port5678
Instances1. The n8n editor should not run on multiple instances without a dedicated queue setup.
Persistent storageYes, 5 GB, directory /home/node/.n8n

Pick a name between 6 and 32 characters, using lowercase letters, numbers, and hyphens; it also defines the *.clients.zenifra.com address. For testing, hourly billing is the cheapest; for continuous use, compare it with monthly.

Storage

Required. Workflows, credentials, and execution history live in this directory; without it, everything is lost on restart.

Step 2: configure environment variables

Add the variables below in the Environment variables step:

N8N_HOST=<your-address>.clients.zenifra.com
N8N_PORT=5678
N8N_PROTOCOL=https
WEBHOOK_URL=https://<your-address>.clients.zenifra.com/
N8N_ENCRYPTION_KEY=<long-random-key>
GENERIC_TIMEZONE=America/Sao_Paulo

Keep N8N_ENCRYPTION_KEY safe: it encrypts saved credentials and must stay the same across versions. If you use a custom domain, update the address in N8N_HOST and WEBHOOK_URL. See Environment variables.

Step 3: create and validate

Review the estimated cost and click Create Project. When it finishes, the console opens the project page with the public address.

Open the project URL. On first access, n8n asks you to create the owner account: create it right away, before sharing the address. Then create a workflow with a Webhook node and confirm the URL shown uses the address configured in WEBHOOK_URL.

If the application does not respond, check the project logs, the configured port, and the troubleshooting guide.

Production recommendations

  • Use the monthly model for automations running 24/7.
  • For many workflows, connect n8n to a managed PostgreSQL instead of the default local database.
  • Restrict the editor by IP with access control when your plan allows it.

To remove the project, open it in Projects and click Delete. Deletion is permanent and erases storage.

Next steps

Last updated on

On this page