Does n8n require consent on my website?

No consent is required for n8n. It operates entirely as a backend automation service with no client-side scripts, no cookies, and no browser-side data collection on visitor-facing pages. Any data processed through n8n workflows is governed by the site operator's backend privacy practices.

What does n8n do in the browser?

n8n does not load JavaScript or set any cookies in website visitors' browsers. All n8n workflow execution occurs server-side, triggered by webhooks, scheduled events, or API calls. The website may reference n8n webhook endpoints but n8n itself injects nothing into the visitor's browser.

How does ConsentStack handle n8n?

ConsentStack has no consent gate to apply for n8n because it has no client-side presence. If ConsentStack detects n8n through webhook endpoint patterns or infrastructure signatures, it flags it as functional with no blocking action required for consent compliance.

What tracker domains does n8n use?

ConsentStack has catalogued tracker domains for n8n including n8n.io. These are the network destinations n8n's scripts contact, which a consent platform blocks until a visitor agrees.

n8n - Workflow Automation & Privacy Consent Profile

Back to Vendor Library

Overview

n8n is an open-source, self-hostable workflow automation platform that enables users to connect APIs and services through a visual node-based editor. Unlike cloud-only automation tools, n8n can be deployed on-premises, giving organizations full control over their data flows. When ConsentStack detects n8n, it typically indicates the website uses n8n-powered backend workflows — the platform has no direct client-side script presence on visitor-facing pages.

What This Script Does

n8n operates entirely as a backend automation service with no browser-side scripts on visitor-facing pages.

No client-side scripts: n8n does not load JavaScript or set cookies in website visitors' browsers. All workflow execution happens server-side.
No cookies set: No cookies, localStorage, or sessionStorage entries are created on visitor-facing pages.
Backend operation: n8n workflows execute on the server, triggered by webhooks, scheduled events, or API calls from the website's backend. Workflows connect to external services (databases, APIs, email providers, CRMs) entirely server-to-server.
Webhook endpoints: The website may expose n8n webhook URLs (e.g., n8n.example.com/webhook/...) that receive form submissions or event data from the frontend, but the n8n application itself does not inject scripts into the visitor's browser.
Detection context: ConsentStack may detect n8n through webhook endpoint patterns, API references, or infrastructure signatures, even though no visitor-facing scripts are present.

Consent & Compliance

n8n falls under the functional consent category.

Under GDPR and ePrivacy, n8n has no ePrivacy cookie consent implications as it does not set cookies or store data on the visitor's device. Data processed through n8n workflows (form submissions, webhook payloads) is personal data under GDPR, but this processing is managed server-side under the site operator's data processing policies, not through client-side tracking.

Under CCPA/CPRA, data routed through n8n workflows constitutes personal information governed by the site operator's privacy practices. n8n's self-hostable architecture means data stays within the operator's infrastructure.

Should You Block This Without Consent?

No. n8n has no client-side presence — no scripts, no cookies, no browser-side data collection. There is nothing to block from a consent management perspective. Data processing concerns are addressed through the site's backend privacy practices, not through cookie consent.

Is n8n GDPR compliant?

n8n typically loads functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So n8n can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads n8n, not on n8n itself.

Visit website