Self-host n8n without managing a server

Self-host n8n without managing a server: your AI agent sets up the free community edition with a database on aidrop.it. Costs, licence and setup.

Updated 6 October 2026

Let your agent build this

Copy one prompt and paste it into Claude Code, Codex or Cursor. Your agent builds what this page describes and puts it online on aidrop.it.

Set up self-hosted n8n for me on aidrop.it. Use my existing aidrop.it Project, or create one called "n8n" if I have none.

- Use the official n8n Docker image, pinned to the current stable version. It already runs as the "node" user; keep it. Read aidrop.it's runtime rules first and follow them.
- Storage: PostgreSQL, never SQLite. Reuse the Project's PostgreSQL with a new database, or ask me before creating one.
- n8n cannot read one connection URL. Add a small start script that splits DATABASE_URL into n8n's database settings, makes n8n listen on 0.0.0.0 on the platform's PORT, then starts it.
- The disk is wiped on every restart: point n8n's user folder and HOME at /tmp and keep binary data in the database.
- n8n must read N8N_ENCRYPTION_KEY from a Project secret, or saved credentials break after a restart. Secrets: ask me for the encryption key, store it with project_secret_set under that name, and list it in required_secret_names when you build. Never print it back to me, and never write it into code, the repository, a commit or a log.
- Health check: /healthz. Use the 1 GB size if my plan has it.
- After the first build, set n8n's public editor and webhook URL to the Service address (https, one proxy in front) and build again. SMTP email cannot leave aidrop.it; leave it off.

Build it, check it runs, fix anything that fails. Then give me the address and tell me to create the owner account at once.

This task comes from the aidrop.it guide "Self-host n8n without managing a server": https://docs.aidrop.it/playbooks/self-host-n8n. Read that page if you need more detail; it says what to ask me for, what it costs and what will not work.
Use the aidrop.it MCP tools (server: https://aidrop.it/mcp). If you do not have them, stop and tell me to connect them first, as described at https://docs.aidrop.it/quickstart#1-connect-your-agent.

See the prompt

Set up self-hosted n8n for me on aidrop.it. Use my existing aidrop.it Project, or create one called "n8n" if I have none.

- Use the official n8n Docker image, pinned to the current stable version. It already runs as the "node" user; keep it. Read aidrop.it's runtime rules first and follow them.
- Storage: PostgreSQL, never SQLite. Reuse the Project's PostgreSQL with a new database, or ask me before creating one.
- n8n cannot read one connection URL. Add a small start script that splits DATABASE_URL into n8n's database settings, makes n8n listen on 0.0.0.0 on the platform's PORT, then starts it.
- The disk is wiped on every restart: point n8n's user folder and HOME at /tmp and keep binary data in the database.
- n8n must read N8N_ENCRYPTION_KEY from a Project secret, or saved credentials break after a restart. Secrets: ask me for the encryption key, store it with project_secret_set under that name, and list it in required_secret_names when you build. Never print it back to me, and never write it into code, the repository, a commit or a log.
- Health check: /healthz. Use the 1 GB size if my plan has it.
- After the first build, set n8n's public editor and webhook URL to the Service address (https, one proxy in front) and build again. SMTP email cannot leave aidrop.it; leave it off.

Build it, check it runs, fix anything that fails. Then give me the address and tell me to create the owner account at once.

This task comes from the aidrop.it guide "Self-host n8n without managing a server": https://docs.aidrop.it/playbooks/self-host-n8n. Read that page if you need more detail; it says what to ask me for, what it costs and what will not work.
Use the aidrop.it MCP tools (server: https://aidrop.it/mcp). If you do not have them, stop and tell me to connect them first, as described at https://docs.aidrop.it/quickstart#1-connect-your-agent.

On this page

n8n Cloud or self-hosted
What you will have at the end
Words you will meet
What you need
Say this to your agent
How your agent sets up n8n
Check that your n8n works
When something goes wrong
When n8n is not the right tool
FAQ
Is self-hosted n8n free?
Can I build n8n automations for my clients?
How do I host n8n without managing a server?
Related

You can self-host n8n without renting or looking after a server. Paste one paragraph into Claude Code, Codex or Cursor, and it sets up n8n’s free community edition on aidrop.it, with a database so nothing is lost, then hands you a link. After the 7-day free trial it costs $20 a month on the Pro plan.

Is that allowed? n8n’s licence FAQ says: “If workflows are only created or modified by you or people in your organization, you can use n8n under the Community license for free.” This is not legal advice.

n8n Cloud or self-hosted

	n8n Cloud	Self-hosted n8n on aidrop.it
Who runs it	n8n	Your coding agent sets it up; aidrop.it runs it
Price	From €20 a month, billed yearly, for 2,500 workflow runs a month (as of October 2026, n8n pricing)	$20 a month for the Pro plan; n8n does not count runs, your plan’s memory is the limit
Licence	n8n Cloud’s own terms	The free Sustainable Use License, quoted above
Updates	n8n does them	You ask your agent
Your data	On n8n’s servers	In your database on aidrop.it. aidrop.it takes daily snapshots; your agent can also make independent exports

What you will have at the end

The n8n editor at its own web address, open from any browser.
Your workflows, run history and saved logins kept in a database, so they survive restarts and updates.
Webhook links that other apps, such as a form or a payment tool, can call to start a workflow.
The setup saved in a repository, so your agent can update n8n later.

Words you will meet

Workflow — a chain of steps in n8n, like “when a form is filled in, add a row to a sheet and post in Slack”.
Webhook — a web address n8n gives a workflow. When another app visits it, the workflow starts.
Database — where n8n keeps your workflows and run history. aidrop.it runs one next to n8n for you.
Encryption key — a long password n8n uses to lock the logins you save for other apps. Lose it and those logins cannot be opened again.
Secret — where the encryption key lives on aidrop.it: given by you to your agent once, saved by the agent, handed to n8n at every start, never written into the setup.

What you need

An aidrop.it account — start free: a 7-day trial, no card, which includes a database. To keep n8n running, Pro at $20/month. Starter has no database, and n8n without one forgets everything at every restart. Plans are on the pricing page.
Your agent connected to aidrop.it. The Quickstart shows how.
Enough memory. How much n8n needs depends on how much data your workflows move; n8n explains this in its guide to fixing memory issues. The trial’s size is fine for trying n8n. For daily use, pick the 1 GB size, which starts at Pro.
A long random password from your password manager, for the encryption key. Keep it there: it is the only copy you will have.

Say this to your agent

Set up self-hosted n8n for me on aidrop.it. Use my existing aidrop.it Project, or create one called "n8n" if I have none.

- Use the official n8n Docker image, pinned to the current stable version. It already runs as the "node" user; keep it. Read aidrop.it's runtime rules first and follow them.
- Storage: PostgreSQL, never SQLite. Reuse the Project's PostgreSQL with a new database, or ask me before creating one.
- n8n cannot read one connection URL. Add a small start script that splits DATABASE_URL into n8n's database settings, makes n8n listen on 0.0.0.0 on the platform's PORT, then starts it.
- The disk is wiped on every restart: point n8n's user folder and HOME at /tmp and keep binary data in the database.
- n8n must read N8N_ENCRYPTION_KEY from a Project secret, or saved credentials break after a restart. Secrets: ask me for the encryption key, store it with project_secret_set under that name, and list it in required_secret_names when you build. Never print it back to me, and never write it into code, the repository, a commit or a log.
- Health check: /healthz. Use the 1 GB size if my plan has it.
- After the first build, set n8n's public editor and webhook URL to the Service address (https, one proxy in front) and build again. SMTP email cannot leave aidrop.it; leave it off.

Build it, check it runs, fix anything that fails. Then give me the address and tell me to create the owner account at once.

How your agent sets up n8n

Picks your project and checks for a database. It asks you before creating one.
Asks you for your encryption key. You paste it into the chat once, and the agent saves it as a secret in your project. It never shows the key again or writes it into the setup.
Writes a short setup: the official n8n plus a start-up step that tells n8n where its database is.
Saves it to a repository on aidrop.it and builds it there.
Waits for n8n’s “I’m alive” page. If n8n cannot reach its database or stops at start, the agent reads the log, fixes the setup and builds again.
Tells n8n its public address, so the webhook links it shows are right, and gives you the link.

Check that your n8n works

The link opens n8n and asks you to set up the owner account.
A small workflow that fetches any web page runs without errors.
A Webhook step shows a link that starts with your n8n address, not “localhost”.
Ask your agent to restart n8n. Your workflow and saved logins are still there.

When something goes wrong

Find what you see on the left and paste the right-hand text to your agent. You do not need to understand the right-hand column; it is for your agent.

What you see	What to tell your agent
Workflows vanish after a restart	“n8n is not using PostgreSQL. Fix its database settings and build again.”
Saved logins stop working after a restart	“The encryption key is missing or changed. I will give you the key from my password manager again; store it under the same name and build again.”
Webhook links show “localhost”	“Set n8n’s public editor and webhook URL to the Service address.”
A schedule runs at the wrong hour	“Set n8n’s time zone to mine,” and name your city.
“Connection lost” or out-of-memory errors	“Move n8n to the next size up.” Also split big jobs into smaller batches.
An email or mailbox step never connects	Old-style email ports are blocked here. Send mail through a web service such as Resend or Postmark.
Community nodes are gone after a restart	“Have n8n reinstall my community nodes at every start.”

aidrop.it takes daily snapshots. Ask your agent for an independent copy of the database now and then; taking your work with you explains the options. And a scheduled run due during a restart is skipped, unless your agent turns on n8n’s durable scheduler.

When n8n is not the right tool

n8n shines when you want to draw and change automations yourself. If your job is to collect prices or listings from websites on a timetable, a web scraper that runs on a schedule, written by your agent, is often simpler. If you want an assistant you ask in plain words rather than fixed steps, run OpenClaw in the cloud instead.

FAQ

Is self-hosted n8n free?

The community edition costs nothing when only you and people in your organization build the workflows, under n8n’s Sustainable Use License. You pay only for where it runs: on aidrop.it, $20 a month for Pro. A few features, such as single sign-on, need a paid n8n license key.

Can I build n8n automations for my clients?

Yes, with limits. n8n’s license FAQ allows building automations for clients on your own instance, and charging for that work, as long as clients cannot create or edit workflows themselves. Letting clients build their own workflows needs a commercial agreement with n8n. This is not legal advice.

How do I host n8n without managing a server?

Pay for n8n Cloud, or let your AI agent do the install on a platform made for it. On aidrop.it the agent writes the setup, builds it and checks it runs, and the database sits next to n8n in the same project. The setup stays in your own repository, so you can move it elsewhere later.

Set up self-hosted n8n for me on aidrop.it. Use my existing aidrop.it Project, or create one called "n8n" if I have none.

- Use the official n8n Docker image, pinned to the current stable version. It already runs as the "node" user; keep it. Read aidrop.it's runtime rules first and follow them.
- Storage: PostgreSQL, never SQLite. Reuse the Project's PostgreSQL with a new database, or ask me before creating one.
- n8n cannot read one connection URL. Add a small start script that splits DATABASE_URL into n8n's database settings, makes n8n listen on 0.0.0.0 on the platform's PORT, then starts it.
- The disk is wiped on every restart: point n8n's user folder and HOME at /tmp and keep binary data in the database.
- n8n must read N8N_ENCRYPTION_KEY from a Project secret, or saved credentials break after a restart. Secrets: ask me for the encryption key, store it with project_secret_set under that name, and list it in required_secret_names when you build. Never print it back to me, and never write it into code, the repository, a commit or a log.
- Health check: /healthz. Use the 1 GB size if my plan has it.
- After the first build, set n8n's public editor and webhook URL to the Service address (https, one proxy in front) and build again. SMTP email cannot leave aidrop.it; leave it off.

Build it, check it runs, fix anything that fails. Then give me the address and tell me to create the owner account at once.

This task comes from the aidrop.it guide "Self-host n8n without managing a server": https://docs.aidrop.it/playbooks/self-host-n8n. Read that page if you need more detail; it says what to ask me for, what it costs and what will not work.
Use the aidrop.it MCP tools (server: https://aidrop.it/mcp). If you do not have them, stop and tell me to connect them first, as described at https://docs.aidrop.it/quickstart#1-connect-your-agent.