n8n.io - Zappier, IFTTT, Integromat alternative

[hiyukoim]

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

[imc67]

This is something! +1 from me

[jdaviescoates]

@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

[imc67]

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

[yusf]

Any signs of LDAP?

[mehdi]

I would love to see this too

[jimcavoli]

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.

[nebulon]

@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.

[hiyukoim]

@jdaviescoates
haha,sure, of course I did

[msbt]

Hey @jimcavoli, good job with n8n, I've cloned your repo and played around a little. For whatever reason the basic auth wasn't working out of the box, so I added ENV N8N_CONFIG_FILES="/app/data/.n8n/config" to the Dockerfile. Now auth works, but as soon as you restart the app for the first time, it won't come up anymore with that errormessage: Error: configuration param 'encryptionKey' not declared in the schema. It only gets back online after removing the encryptionKey entry in /app/data/.n8n/config and triggering another restart (which then again sets a new/different encryptionKey ).

Any idea what's that about, or how did you get auth to work? It just ignores my settings without that env variable. If it's not set, restarts work, but auth does not.

A quick fix was to add another env var ENV N8N_ENCRYPTION_KEY="123" to make the encryption key static (still had to delete it before restarting, but it sets the static one afterwards), else all saved credentials were unusable after restart and changed encryptionKey. Oviously that's not a solution, but at least I could test a little.

Other than that (and updating to the latest version, base image and some minor tweaks) it seems to be working fine!

edit: not able to get webhooks to work, not sure if it's me or n8n

[imc67]

Today IFTTT announced that they will charge you $10 a month (!!!!) for their service. Maybe now it’s really time to put Cloudron in a unique position with this app?!

[girish]

@imc67 Interesting. So existing free users have to pay or are they grand fathered?

[imc67]

@girish https://ifttt.com/plans
Create 3 Applets of your own
Turn on unlimited Applets

[jdaviescoates]

@imc67 looks like perhaps there was a backlash, can now "set your price" starting at $1.99/mo

[imc67]

Got an email a few minutes ago from IFTTT;

Note: the free-forever IFTTT Standard plan no longer supports creating unlimited Applets from scratch.

To date, you’ve created more than 3 Applets. If you do not upgrade to Pro, all but 3 of your created Applets will be archived.

[jdaviescoates]

@imc67 yeah, I've got the same thing.

Most significantly, I think, is the last sentence:

Your current plan, the free-forever IFTTT Standard plan, no longer supports creating unlimited Applets from scratch.

To date, you’ve created more than 3 Applets. If you do not upgrade to Pro before October 7th, all but 3 of your custom Applets will be automatically archived.

For more information about archived Applets, see What happens if I do not upgrade to IFTTT Pro?

Through October 7th, you may set the monthly price you want to pay to upgrade to Pro and we’ll honor it forever.

Seems the Set your price options I mentioned above will likely disappear on October 7th... So I guess if you use IFTTT a lot it might be a good idea to pay $1.99/mo now (I actually hardly ever use it these days so think I'll just use self-hosted alternatives once they've been packaged for Cloudron).

[A Former User]

Would definitely be interested in this. Specifically, my use-case is building my own smart light switches. Id have the buttons hooked up to microcontrollers that send requests to something like IFTTT or n8n off of a webhook trigger to turn lights on/off.

[mehdi]

@atrilahiji For this I suggest installing home-assistant locally on something like a raspberry pi, locally. I actually just installed such a system at my place

[girish]

I looked into this a bit. Did I get it right that this app only supports basic auth? That's kinda worrying. I am surprised though given that it seems to have a lot of github stars atleast.

[A Former User]

Thats what im seeing. Being able to use LDAP for this would be a godsend but I didnt find info on using LDAP with it. RIP the IFTTT alternative dream?