Skip to content

title: n8n description: n8n is workflow automation: flows built from nodes that call APIs, transform data and react to webhooks, with a PostgreSQL database for the flows and, as an opt

n8n

What is it

n8n is workflow automation: flows built from nodes that call APIs, transform data and react to webhooks, with a PostgreSQL database for the flows and, as an option, a queue mode with workers for heavier loads.

The platform offers it as a managed application: an Argo CD Application the platform creates for you - from the shop or from the marketplace's n8n (managed) template - and keeps in sync with the chart. Its secrets are generated once at deployment, its hostname sits on the app domain of your cluster, and the platform watches its health. The same chart installed by you (helm install, or the plain template) is unmanaged: it runs in your project like any other workload, and nothing on the platform side follows it.

How to create

Through the marketplace. In the console (web.grn.cloud) open the Developer Catalog, choose n8n (managed) and fill in the application name, the hostname, the volume size and the queue mode. The result is an Application in your home project; its resource tree shows the project it creates and what runs in it. The deployment also appears as an order in the shop, so your account lists every application you run; a paid product is billed from the day of the deployment.

Through the shop. n8n is not in the shop yet; use the marketplace.

How to make changes

Configuration lives in the Application: open it in the GitOps page of the console, and the YAML tab shows the chart values under spec.source.helm.valuesObject - that is where the encryption key and the redis password are read. Values the platform set for you (the hostname, the generated secrets) are kept; the other values are yours to change, and Argo CD applies the change at the next sync. Change the settings of an application walks through it.

The chart version is the Application's targetRevision; raising it upgrades the application at the next sync, lowering it is a downgrade the chart must support. Versions, upgrades and removal covers it.

How to cancel

Delete the Application in the GitOps page; the project it created and everything in it go with it, and the order line in the shop ends within the hour.

Deletion removes the application's data with it. Make and keep your own backup before you delete: the platform keeps none for you.

References