n8n - an open source, self hosted info transform & workflow automation tool w/ drag and drop ease.

==== LINKS ====
Show Notes

n8n Discount Code

n8n Website

n8n Video Series on YouTube

Baserow Video

Poll Link from Baserow

Support my Channel and ongoing efforts through Patreon:

==== TIMESTAMPS ====
00:00 Beginning
00:09 About n8n
01:45 Thank you to my Patrons over at Patrion, and my subscribers on YouTube
02:20 Supporting n8n Open Source / Pricing (Discount Code in Description)
06:09 Documentation of Self Hosting
09:25 Installing n8n on Docker
14:40 Testing our New Install
15:05 Setup a Revers Proxy with a Subdomain
17:05 Initial Setup of n8n (first run)
17:50 Using the n8n Web Interface
20:55 About Webhooks in n8n
22:45 Setting up a full Workflow Example in n8n
33:40 Checking Workflow Executions in Production mode

=== Contact ===
Twitter: @mickintx
Telegram: @MickInTx
Mastodon: http://mastodon.partecipa.digital/ @MickInTX

Try out SSDNodes VPS Services! Amazing Specs for incredibly low costs. I’m running a 32 GB RAM / $ CPU Server for only $9 a month! Seriously. FOr long term server usage, this is the way to go!

Get a $50.00 credit for Digital Ocean by signing up with this link:

Use Hover as your Domain Name Registrar to get some great control over you domains / sub-domains:

Support my Channel and ongoing efforts through Patreon:

What does the money go to?
To Pay for Digital Ocean droplets, donations to open source projects I feature, any hardware I may need to purchase for future episodes (which I will then give to a subscriber in a drawing or contest).

=== Attributions ===
Intro and Outro music provided by https://www.bensound.com

21 thoughts on “n8n – an open source, self hosted info transform & workflow automation tool w/ drag and drop ease.”
  1. Love your content, but your take on the licenses is factually incorrect. Partly because Jan misrepresents their license, I believe.

    First, please don't refer to fair-code licenses as open source. Jan doesn't even do this (any more) and strictly refers to it as source-available.
    A key feature of open source is the ability to use the software for any purpose and the ability to fork the software and take it in your own direction.
    Fair-code does not allow you to do this.
    Fair-code is functionally identical to freeware, but with the ability to view the code.

    Second, you refer to the old license as "Apache 2.0 GPL". This is incorrect. The old license was Apache 2.0 with Commons Clause.
    GPL is a completely different set of licenses made by the Free Software Foundation and are not related at all.

    Third, Jan understates how restrictive the Sustainable Use License (SUL) is, compared to the Commons Clause.
    The SUL prohibits ALL commercial external use and requires a particular license for embedding it in other solutions (n8n.embed). The Commons Clause allows for this, as long as the value of the product is not derived "entirely or substantially, from the functionality of the [fair-code] Software"

    E.g. if Home Assistant wanted to use n8n for automations, nobody would be allowed to sell HA products without paying for n8n.embed licenses.
    With Apache 2.0 with Commons Clause, they would.

    This may sound like a minor issue, but HA is made up of hundreds of moving parts. What would the open source world look like, if every component had their own license fees attached?

    Fourth, As Chandan Puri mentioned, the software is owned entirely by the company n8n and if they go bust, change direction, sell the project or simply change to a closed source model, you're completely locked out, just like you would be with normal proprietary software.

    I am not against fair-code software at all, but it's important to recognize that for all practical intents and purposes, this is closer to freeware, than to open source.

  2. Hi, I always looking forward to your videos about self hosted open source. Do you know anything about some self hosted app to manage and or monitor health of family members?

  3. It has a restriction on selling the software as a service. So if the current maintainers go under there wouldn't be much financial incentive for anyone else to continue development. That isn't open source, its code available and free for internal use.

Leave a Reply

Your email address will not be published.