From 8ac6ce5ddd92009d5b95e718d2d6cf873de10753 Mon Sep 17 00:00:00 2001 From: Jon Date: Tue, 16 Dec 2025 11:33:04 +0000 Subject: [PATCH] Document default exclude nodes (#4023) Co-authored-by: Tomi Turtiainen <10324676+tomi@users.noreply.github.com> --- .../builtin/core-nodes/n8n-nodes-base.localfiletrigger.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.localfiletrigger.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.localfiletrigger.md index a970a95a3..8eb974c76 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.localfiletrigger.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-base.localfiletrigger.md @@ -9,9 +9,13 @@ priority: high The Local File Trigger node starts a workflow when it detects changes on the file system. These changes involve a file or folder getting added, changed, or deleted. +/// warning | Security considerations +The Local File Trigger node can introduce significant security risks in environments that operate with untrusted users. Because of this, the node is [disabled](/hosting/securing/blocking-nodes.md#exclude-nodes) by default starting from version 2.0. +/// + /// note | Self-hosted n8n only This node isn't available on n8n Cloud. -/// +/// ## Node parameters