Package Details: n8n 2.30.7-1

Git Clone URL: https://aur.archlinux.org/n8n.git (read-only, click to copy)
Package Base: n8n
Description: Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.
Upstream URL: https://n8n.io
Licenses: custom:Sustainable Use License
Submitter: evine
Maintainer: lapsus
Last Packager: lapsus
Votes: 3
Popularity: 0.000108
First Submitted: 2024-06-19 15:02 (UTC)
Last Updated: 2026-07-17 09:36 (UTC)

Latest Comments

ggordebeke commented on 2026-07-01 18:46 (UTC)

Last 2 versions have a bug: https://github.com/n8n-io/n8n/issues/33370 Not sure if the above situation also requires a change in the PKGBUILD.

Dominiquini commented on 2026-06-24 23:36 (UTC)

Can you add the option '!strip' to the PKGBUILD? The stripping process take forever on my machine everytime this package updates!:

options=('!debug' '!strip')

Dominiquini commented on 2026-03-04 19:27 (UTC)

n8n now support "engines": { "node": ">= 22.16" }, Can you please update the pkg

lapsus commented on 2025-10-01 08:49 (UTC)

Thank you for suggestion, must be aboard now

danirod commented on 2025-09-29 22:51 (UTC)

To opt-out from data collection after installation, the following lines should be added to /etc/defaults/n8n file after installation, as described in the docs (https://docs.n8n.io/hosting/configuration/configuration-examples/isolation/):

N8N_DIAGNOSTICS_ENABLED=false
N8N_VERSION_NOTIFICATIONS_ENABLED=false
N8N_TEMPLATES_ENABLED=false

I understand that packages from the AUR are not subject to the same telemetry and data collection principles as official packages, but for the version notifications, this might be overlapping the job of an AUR package manager.

hellarrived commented on 2025-08-06 08:47 (UTC)

n8n now support "engines": { "node": ">=20.19 <= 24.x" }, Can you please update the pkg

lapsus commented on 2025-07-15 12:02 (UTC)

Oops, thanks for spotting, gotta fix

shm commented on 2025-07-15 10:14 (UTC) (edited on 2025-07-15 10:20 (UTC) by shm)

Is it really conflicting with nodejs>=23? Which way? If you need to restrict dependency version use something like depends=('foobar>=1.8.0' 'foobar<2.0.0')