Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


n8n.io - Zappier, IFTTT, Integromat alternative



  • @jdaviescoates When this came out, the license was not Common Clause. 😛

    But now that we know the license and indeed Cloudron can redistribute it, I'm all for this to be ported here. 🙂



  • +1!
    I'm looking forward to see this app as cloudron app!



  • This is something! +1 from me



  • @hiyukoim said in n8n.io - Zappier, IFTTT, Integromat alternative:

    +1!
    I'm looking forward to see this app as cloudron app!

    @imc67 said in n8n.io - Zappier, IFTTT, Integromat alternative:

    This is something! +1 from me

    Just to be sure, have you both clicked on the little up ^ arrow on the post at the top of this thread?

    Because that's how to +1 in a way that counts 😉



  • Just to be sure, have you both clicked on the little up ^ arrow on the post at the top of this thread?

    Because that's how to +1 in a way that counts 😉

    haha, ofcourse 👍



  • Any signs of LDAP?



  • I would love to see this too



  • So I have an initial packaging for this done at https://git.cloudron.io/jimcavoli/n8n-app

    HOWEVER, I'm honestly not sure I'd be comfortable putting this software into production as-is. It's pretty weak on some security features, but maybe its not the end of the world for people and I'm just super paranoid. There seems to be an undocumented way to do JWT auth, which I'm not going to even try to get into that, since I'm only aware of it from looking at the config file handling typescript code. The only supported authentication right now is basic auth as documented - with a single username/password set by ENV or config file (I went with the latter since it's easier for end-users to edit in /app/data/.n8n/config by terminal).

    Either way, everything basically works, and by launching via supervisord with the working directory set to /app/data/output we're able to contain its binary file writing to system (probably a bad thing to do in prod as well, but it works).

    Custom nodes can be added to /app/data/custom, the config file is JSON at /app/data/.n8n/config, and the package writes cloudron-provided postgresql configuration to that file at launch.

    Some stuff only works in Chrome. That's just an issue with the app. Something about they way they're handling web sockets means other browsers see "Connection lost" in the top right, which is where the Activation toggle should be. Most other things actually work fine, but that's necessary for executing workflows in-browser manually and activating them.

    I packaged this one because it seems to have some popularity in asks, but it definitely deserves some due diligence before heading to production for anyone or the app store. It's also pre-1.0 so not sure how much is changing how fast, and the setup as is was a pretty delicate thing to get done. Maybe my concerns are overplayed, maybe not, but either way, there's something we can start to kick the tires on for this app now.


  • Staff

    @jimcavoli thanks for looking into this! The upstream projects seems to be quite active, so that is a good sign and probably things will improve then.

    I've put it on my task list to take a look and then possiblly port it to the new base image and add some tests.



  • @jdaviescoates
    haha,sure, of course I did ❤


Log in to reply