n8n.io - Zappier, IFTTT, Integromat alternative
-
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.
-
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?
-
Just chatting with @murgero to look at this. Please pledge some sponsorship if you want, and to respectfully keep devs fed for finishing what we can't: https://forum.cloudron.io/topic/3380/sponsoring-n8n
-
It may end up that Huginn is the better option. Not sure, but that's a Ruby/Rails app too (my primary speciality) so perhaps I can look at getting that packaged so a bit of comparison can begin. Honestly not sure where that rings in on my priority list for the time being though. Reasonably low through the early parts of next year, likely.
-
It may end up that Huginn is the better option. Not sure, but that's a Ruby/Rails app too (my primary speciality) so perhaps I can look at getting that packaged so a bit of comparison can begin. Honestly not sure where that rings in on my priority list for the time being though. Reasonably low through the early parts of next year, likely.
@jimcavoli happy to sponsor if you do. We did trial it and ended up sticking with NodeRED.
TBH, with ETL tools, it's inevitable to use multiple as the time-saving from having read-made connectors offsets the cost of having different automations in different tools, hence we still run 4 and would likely hedge bets, continuing to use each for their advantages than limiting ourselves to just one.
-
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/configby terminal).Either way, everything basically works, and by launching via supervisord with the working directory set to
/app/data/outputwe'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.
@jimcavoli Nice work and insight. Does this development change anything for your view on the limitations of basic auth? https://forum.cloudron.io/topic/3682/proxyauth-addon
As far as "Some stuff only works in Chrome". I guess that covers all Chromiums, as I tend to use Vivaldi in those cases.
As with all these Apps, I can get some developer assistance if we need to also contribute direct to the apps themselves, so it's always worth having them available in the App Store as "Unstable" so we can review these things and contribute upstream with sponsorship or dev-time as well if necessary.
Web Design https://www.evergreen.je
Development https://brandlight.org
Life https://marcusquinn.com -
@jimcavoli Nice work and insight. Does this development change anything for your view on the limitations of basic auth? https://forum.cloudron.io/topic/3682/proxyauth-addon
As far as "Some stuff only works in Chrome". I guess that covers all Chromiums, as I tend to use Vivaldi in those cases.
As with all these Apps, I can get some developer assistance if we need to also contribute direct to the apps themselves, so it's always worth having them available in the App Store as "Unstable" so we can review these things and contribute upstream with sponsorship or dev-time as well if necessary.
-
@marcusquinn Yeah, maybe the new auth wall is enough. Haven't tried adding it to this packaging yet, but that could be a reasonable solution, since this is otherwise fairly ready to go and has a lot of asks.
@jimcavoli think you could pick this up for a little sponsoring contribution? I think @murgero has other understandable priorities at the mo, so I prefer not to chase.
https://forum.cloudron.io/topic/3380/sponsoring-n8n
We have can jump in and start using and looking at core contributions as well once it's running and we can battle test. We have more devs on our team that can get into packaging but right now they are all flat-out on a bunch of systems migrations.
-
I think this one should just wait for Cloudron@6 and use the integrated proxyAuth. It does not seem reasonable to come up with a custom solution just to roll-back in a few weeks
@mehdi fair enough. I'm working on getting more Dev attention to help on Cloudron stuff too, takes a little time but as soon as anyone gets involved they do see the light
-
I'm reworking this now that 6 is out and
proxyAuthis an option. Currently got the latest version building and running on the latest node. Waiting for some details on how to doproxyAuthconfiguration to not break webhooks (rather important for this one!) and then I'll need to get to fixing up the websockets, but overall is looking okay. Switching from file-based to env-based configuration only because it seems better supported by the docs as well. -
I'm reworking this now that 6 is out and
proxyAuthis an option. Currently got the latest version building and running on the latest node. Waiting for some details on how to doproxyAuthconfiguration to not break webhooks (rather important for this one!) and then I'll need to get to fixing up the websockets, but overall is looking okay. Switching from file-based to env-based configuration only because it seems better supported by the docs as well. -
I'm reworking this now that 6 is out and
proxyAuthis an option. Currently got the latest version building and running on the latest node. Waiting for some details on how to doproxyAuthconfiguration to not break webhooks (rather important for this one!) and then I'll need to get to fixing up the websockets, but overall is looking okay. Switching from file-based to env-based configuration only because it seems better supported by the docs as well.@jimcavoli would love to see this in action! It seems that your repo hasn't been updated in a while (I'm only seeing 1 commit there) and the 'active connection to the server' isn't working so I'm not able to run any workflows. Keeping an eye on this for sure. Thanks!
-
Incredibly excited for this! Thanks for your hard work!!!
-
I'm reworking this now that 6 is out and
proxyAuthis an option. Currently got the latest version building and running on the latest node. Waiting for some details on how to doproxyAuthconfiguration to not break webhooks (rather important for this one!) and then I'll need to get to fixing up the websockets, but overall is looking okay. Switching from file-based to env-based configuration only because it seems better supported by the docs as well.@jimcavoli @girish @nebulon I just had my Open AI beta application accepted!!
Get me n8n.io on Cloudron and I'll get amazing GPT-3 things built for you!
Web Design https://www.evergreen.je
Development https://brandlight.org
Life https://marcusquinn.com -
@jimcavoli @girish @nebulon I just had my Open AI beta application accepted!!
Get me n8n.io on Cloudron and I'll get amazing GPT-3 things built for you!
@marcusquinn said in n8n.io - Zappier, IFTTT, Integromat alternative:
I'll get amazing GPT-3 things built for you!
Sounds intriguing, what are you thinking?
-
@marcusquinn said in n8n.io - Zappier, IFTTT, Integromat alternative:
I'll get amazing GPT-3 things built for you!
Sounds intriguing, what are you thinking?
@jdaviescoates I think Chatbots are the obvious one but there's a few applications:
- Message/Email context/sentiment analysis for tagging and directing to appropriate staff or place.
- Chat via email.
- CRM enrichment taking all known text from a person and writing a summary.
- Monitoring Social Media for inflammatory messages.
For fun:
Bold text is what you input, the rest is what is written for you:
Or I could ask GPT-3 to answer on my behalf
-
A bit more fun with GPT-3:
-
I'm reworking this now that 6 is out and
proxyAuthis an option. Currently got the latest version building and running on the latest node. Waiting for some details on how to doproxyAuthconfiguration to not break webhooks (rather important for this one!) and then I'll need to get to fixing up the websockets, but overall is looking okay. Switching from file-based to env-based configuration only because it seems better supported by the docs as well.@jimcavoli Hey, how's it going with this? Have you hit any blockers? Just curious if we might see this any time soon. THANK YOU!
