As some advice to prepare for - if this moves any demand from their enterprise pipeline, the n8n team will be looking for ways to add friction to your life and this project.
The easiest will be giving notice that you’re using n8n in the name of the project, and their lawyers will say that this poses great confusion and false affiliation and besmirches their good name etc. etc.
Not sure it’ll happen, but best be prepared and put some headers in that you’re not affiliated, are a community extension, etc
My non-lawyer understanding is that this issue can be reduced by not having the copyrighted name first. So n8n-Oidc might get you flagged, but Oidc-n8n should be fine.
I'm reasonably sure that it's not a hard-and-fast rule. As an easy counterexample, they actively encourage people to publish stuff prefaced with n8n: https://www.npmjs.com/search?q=n8n-nodes-
I meant based on copyright law. I have looked it up before and that's the general consensus I saw.
Basically, if you name your project starting with a copyrighted name like "Android Firewall" and you receive a legal request to change it, you should probably do so. But if your project is "Firewall for Android", the legal request is probably just trying to scare you, ignore it.
If n8n specifically says they're ok with this kind of name then it's ok, of course.
Your plugin is potent, practical, and precise. However, the article itself is a struggle.
It’s not the substance, it’s the style. It’s not the logic, it’s the language. The undisclosed ChatGPT makes the text dense, difficult, and dry. I would rather read the prompt—the plan—than the robotic polish.
I will absolutely use and utilize this tool—it’s a lifesaver—but please: declare AI polish, don't disguise.
/s
That being said, thanks a lot for this tool, I'm geniunely gonna enjoy it. Thanks for making open source n8n useful again!
As some advice to prepare for - if this moves any demand from their enterprise pipeline, the n8n team will be looking for ways to add friction to your life and this project.
The easiest will be giving notice that you’re using n8n in the name of the project, and their lawyers will say that this poses great confusion and false affiliation and besmirches their good name etc. etc.
Not sure it’ll happen, but best be prepared and put some headers in that you’re not affiliated, are a community extension, etc
I'm not worried about it. If they complain, we can address it then.
My non-lawyer understanding is that this issue can be reduced by not having the copyrighted name first. So n8n-Oidc might get you flagged, but Oidc-n8n should be fine.
I'm reasonably sure that it's not a hard-and-fast rule. As an easy counterexample, they actively encourage people to publish stuff prefaced with n8n: https://www.npmjs.com/search?q=n8n-nodes-
I meant based on copyright law. I have looked it up before and that's the general consensus I saw.
Basically, if you name your project starting with a copyrighted name like "Android Firewall" and you receive a legal request to change it, you should probably do so. But if your project is "Firewall for Android", the legal request is probably just trying to scare you, ignore it.
If n8n specifically says they're ok with this kind of name then it's ok, of course.
For the un-briefed:
n8n (pronounced "en-eight-en") means "nodemation," a blend of "node" (for its node-based interface and Node.js) and "-mation" (for automation)
no demation without representation
Author here! AMA
This is really Awesome! Thanks, will try it.
Your plugin is potent, practical, and precise. However, the article itself is a struggle.
It’s not the substance, it’s the style. It’s not the logic, it’s the language. The undisclosed ChatGPT makes the text dense, difficult, and dry. I would rather read the prompt—the plan—than the robotic polish.
I will absolutely use and utilize this tool—it’s a lifesaver—but please: declare AI polish, don't disguise.
/s
That being said, thanks a lot for this tool, I'm geniunely gonna enjoy it. Thanks for making open source n8n useful again!
I'm not sure what led you to this conclusion, but only the code was AI-assisted. The blog post was 100% written by me.