---
title: Deploy n8n with AI on Blossom
url: "/deploy/n8n/"
canonical_url: https://docs.blossom88.com/deploy/n8n/
markdown_url: https://docs.blossom88.com/deploy/n8n.md
summary: Deploy n8n with AI on Blossom. Self-host workflow automation with a private
  editor, managed data, authenticated webhooks, and scalable workers.
categories:
- deployment
- automation
---

# Deploy n8n with AI on Blossom

[n8n](https://n8n.io/) is a workflow automation tool that connects apps and
APIs through a visual editor. Use it to automate tasks triggered by webhooks,
schedules, or events.

Run n8n on Blossom with saved workflows in a managed database and separate
workers that can grow with your automation workload.

[Install the Blossom CLI and skill](/learn/getting-started/install/)
on your agent's machine and choose a Blossom Cloud Location when you log in.
You can also use
[Blossom BYOC (bring your own cloud)](/learn/getting-started/choose-your-cloud/#blossom-byoc).

## Ask Your Agent


> **Ask your AI agent:** Deploy n8n on Blossom with a private editor and workers I can scale.

> Follow this guide: https://docs.blossom88.com/deploy/n8n/



Your agent selects compatible releases and saves the chosen versions in
your deployment configuration. Main and workers use the same n8n image.

| Part | Purpose |
|---|---|
| Main Service | Editor, API, webhook reception, and triggers |
| Queue workers | Execute workflows independently of the editor |
| Managed PostgreSQL | Keeps workflows, credentials, and execution records |
| Managed Redis | Coordinates queued executions |
| Private editor access | Account membership followed by your n8n login |
| Authenticated webhooks | Let external services trigger your workflows |

Create your n8n owner account when the editor first opens. Your agent saves
one `N8N_ENCRYPTION_KEY` and keeps it across main, workers, and app updates
so they can continue reading saved credentials.

**Scale workers for more execution capacity.** Keep one main process for
this queue-mode pattern. Have your agent check n8n's current
[multi-main requirements](https://docs.n8n.io/hosting/scaling/queue-mode/#multi-main-setup)
when planning redundancy for the editor and triggers.

<details class="optional-reading" markdown="1">
<summary>Commands behind the deployment</summary>

Your agent prepares the files using current CLI help and n8n's
[queue-mode requirements](https://docs.n8n.io/hosting/scaling/queue-mode/).
Use the returned resource IDs in place of these examples.

### Create the App and Managed Data

    blossom profile:show
    blossom app:create --data '{"app":{"name":"n8n"}}'

The agent writes environment.yml with your App ID and chosen official image:

```yaml
environment:
  app_id: app-100
  name: production
  source_type: prebuilt_image
  prebuilt_image: <official image pinned by your agent>
  access_mode: members
  access_public_paths:
    - /webhook/*
```

It selects compatible PostgreSQL and Redis releases, resource sizes,
storage, and backups in database_instance.yml and cache_instance.yml.

    blossom environment:create --data environment.yml
    blossom database_instance:create --data database_instance.yml --follow
    blossom database:list --database_instance database_instance-100
    blossom cache_instance:create --data cache_instance.yml --follow
    blossom environment_link:create --data '{"environment_link":{"environment_id":"environment-100","target_type":"Database","target_id":"database-100","var_name":"DATABASE_URL"}}'
    blossom environment_link:create --data '{"environment_link":{"environment_id":"environment-100","target_type":"CacheInstance","target_id":"cache_instance-100","var_name":"REDIS_URL"}}'

### Configure Main and Workers

The agent maps `DATABASE_URL` and `REDIS_URL` to the selected n8n release's
settings, enables queue mode, and chooses shared storage for workflow files.
It keeps the encryption key and connection settings in a private
.env.production file, outside your application repository.

    blossom env_var:push --environment environment-100 --file .env.production

The main Service runs `n8n start`; the worker Service runs `n8n worker`.
The agent chooses worker concurrency, resources, and health checks for your
workflows, and keeps workers private.

    blossom service:create --data web.yml
    blossom service:create --data worker.yml
    blossom environment:deploy --id environment-100 --follow
    blossom environment:show --id environment-100

The agent uses the returned HTTPS URL, or your custom domain, for n8n's
editor and production webhook URLs. It saves those settings and redeploys:

    blossom env_var:push --environment environment-100 --file .env.production
    blossom environment:deploy --id environment-100 --follow

</details>

## Run Your First Workflow


> **Ask your AI agent:** Help me build and test a webhook workflow that requires authentication.

> Follow this guide: https://docs.blossom88.com/deploy/n8n/



Use a **Webhook** node with **Header Auth**, followed by **Respond to Webhook**.
For a simple example, return the incoming request ID. Publish the workflow
and test its **Production URL** with and without authentication.
`/webhook/*` bypasses Blossom's member sign-in; n8n checks the webhook's own
authentication. Keep the editor and `/rest/*` behind Account-member access.

![A published n8n workflow connecting a Webhook node to Respond to Webhook.](/assets/images/n8n/workflow.webp)

<details class="optional-reading" markdown="1">
<summary>Commands to inspect the running App</summary>

    blossom service:list --environment environment-100
    blossom logs --environment environment-100 --lines 30

</details>

## Add Workers


> **Ask your AI agent:** Add more n8n workers and run my workflow again.

> Follow this guide: https://docs.blossom88.com/deploy/n8n/



Workers scale independently of the editor. Your agent chooses a replica
count and concurrency that fit the workload.

<details class="optional-reading" markdown="1">
<summary>Example command to add a worker</summary>

For example, to run two worker Containers:

    blossom service:scale --id service-WORKER --desired-size 2 --follow

</details>

## What You Get

- A private n8n editor and authenticated production webhooks
- Workflows and encrypted credentials in managed PostgreSQL
- Redis-backed queue workers you can scale separately
- Saved data and a stable encryption key across app updates
