Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NODES_INCLUDE not working! #12713

Open
zakariamehbi opened this issue Jan 19, 2025 · 8 comments
Open

NODES_INCLUDE not working! #12713

zakariamehbi opened this issue Jan 19, 2025 · 8 comments
Labels
in linear Issue or PR has been created in Linear for internal review

Comments

@zakariamehbi
Copy link

Bug Description

Hello, I have a problem with NODES_INCLUDE not working, every time I set my list and start my docker container, I get an error when trying to create a trigger.

Error cannot read properties of undefined (reading 'match')
- NODES_INCLUDE=["n8n-nodes-base.gmailTrigger","n8n-nodes-base.gmail","n8n-nodes-base.googleSheets","n8n-nodes-base.httpRequest","n8n-nodes-base.if","n8n-nodes-base.code","n8n-nodes-base.set","n8n-nodes-base.merge","n8n-nodes-base.emailSend","n8n-nodes-base.dateTime","n8n-nodes-base.webhook","n8n-nodes-base.manualTrigger","n8n-nodes-base.scheduleTrigger"]

To Reproduce

  1. Create a docker-compose.yml
  2. Add this config:
version: '3.1'

services:
  n8n:
    image: docker.n8n.io/n8nio/n8n
    ports:
      - "5678:5678"
    environment:
      - NODES_INCLUDE=["n8n-nodes-base.gmailTrigger","n8n-nodes-base.gmail","n8n-nodes-base.googleSheets","n8n-nodes-base.httpRequest","n8n-nodes-base.if","n8n-nodes-base.code","n8n-nodes-base.set","n8n-nodes-base.merge","n8n-nodes-base.emailSend","n8n-nodes-base.dateTime","n8n-nodes-base.webhook","n8n-nodes-base.manualTrigger","n8n-nodes-base.scheduleTrigger"]
    volumes:
      - ~/.n8n:/home/node/.n8n
  1. start the container
  2. try creating a workflow, any trigger will output an error

Expected behavior

  • The list of items included in NODES_INCLUDE shows up, and all the rest disappear.
  • Clicking a trigger doesn't show an error

Operating System

Mac OS

n8n Version

1.74.3

Node.js Version

23.6.0

Database

SQLite (default)

Execution mode

main (default)

@Joffcom
Copy link
Member

Joffcom commented Jan 19, 2025

Hey @zakariamehbi,

We have created an internal ticket to look into this which we will be tracking as "N8N-8169"

@Joffcom Joffcom added the in linear Issue or PR has been created in Linear for internal review label Jan 19, 2025
@zakariamehbi
Copy link
Author

Thank you, after further investigation, NODES_EXCLUDE doesn't exclude anything but doesn't error when trying to create a trigger.

@Joffcom
Copy link
Member

Joffcom commented Jan 20, 2025

Hey @zakariamehbi

I think when using the exclude option while the node appears in the list if you try to use it you will get an error.

I have not tested the include option yet but if you add a node that is on the include list does it also error?

@zakariamehbi
Copy link
Author

zakariamehbi commented Jan 20, 2025

Hello @Joffcom, after testing, when we use the variable NODES_INCLUDE, all of the triggers fail, whether they are on the list or outside of it. The UI shows an error and prevents us from accessing the next step. We're trying to scope n8n to only one trigger and specific apps to achieve a tight integration with our app, which isn't possible without these kinds of settings. Are there any other options we can explore?

Image
Image
Image

@Joffcom
Copy link
Member

Joffcom commented Jan 20, 2025

Hey @zakariamehbi

Can you try 1.75.0 this should have been fixed as part of #12544

@zakariamehbi
Copy link
Author

hey @Joffcom, i'm using the latest docker image, so i should be on the latest version of n8n, but still having this issue.

Image

@zakariamehbi
Copy link
Author

quick update, @Joffcom, after testing with the fixed version 1.75.2 instead of the latest image (for some reason, it's not the latest?), the issue is somewhat resolved. for the apps, we now only see the one defined in NODES_INCLUDE, but for the triggers, we still see the full list, with the only exception being the one not included in NODES_INCLUDE that shows an error message on click.

@despairblue
Copy link
Contributor

after testing with the fixed version 1.75.2 instead of the latest image (for some reason, it's not the latest?)

Releases are tagged as next for a week before they are tagged as latest. That is to iron out issues before most people start using it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in linear Issue or PR has been created in Linear for internal review
Projects
None yet
Development

No branches or pull requests

3 participants