Sponsoring: n8n

[robi]

@girish Simply renaming Unstable to Unsupported will achieve the same effect.

And since you will do best effort anyway, it will be above and beyond what is "advertized" (displayed) and be a net positive.

[A Former User]

@girish I suppose unstable can be re-framed. I think setting expectations and hiding those apps initially would be good. For example:

• The app store has a setting where one has to go to enable the "unstable" section of the store.
• Enabling this has a warning modal asking people to accept all risks associated with installing these.
• Plaster notices everywhere letting people know that support requests for those apps will be ignored.

It is most definitely an issue of expectation management. Working in support, this is something I have to have front of mind always, as anything I do can set a precedent I may not want set. Therefore I have made a point of always being as clear as possible about what I will and will not do.

I guess my proposal of a fan-run unstable app store would step on your toes a bit but it was something I was going to make for myself to basically list apps that point to docker containers I build and then add the ability to use the API to install those apps to any instance.

[marcusquinn]

From our point of view, we're more likely to be able to find time to contribute to fixing things if we've started trialing and expecting to use them in production.

It's not that we can't get apps packaged, it's just not our core business. Our business is implementing what's already available, to focus on business logic that pays for us and apps, platforms, servers, licences, and maybe something left for fun stuff.

I'm happy to share dozens of WP plugins because we had to develop them to get a job done and no-one would know they have any use until we make them exist.

The thing with app packaging, is they are all things that have a proven market and need, usually pretty closely correlated to their GitHub Stars count. So, we're not trying to prove anything to the world, just preserve time for the utility aspect that pays for other things we don't have any business in.

I guess I see it like a utility, I need electricity or WiFi, so does my neighbour, but it gets awkward if ask to borrow theirs.

I've forgotten where I'm going with this - but it feels counter-productive for me to do things that others can do faster at the expense of not doing the things I'm very fast at.

[A Former User]

https://git.atrilahiji.dev/atrilahiji/cloudron-n8n-app

Works

Gotta use chrome/chromium based browser it seems. Firefox gets that connection lost issue.

I did only test with a webhook trigger going to an http request action (which is 99.9% of my use cases) but ymmv. I didn't test much else because I don't use a large number of the services it works with.
This is based largely on @jimcavoli 's package (I literally changed one thing in the manifest).

Install by pulling the repo and doing the while cloudron build/install stuff. Ya know the drill now.

[thetomester13]

@atrilahiji can confirm I'm no longer seeing the 'Connection Lost' on Chrome! (Though still present on Firefox ). Either way, you're my hero! Will be playing around with this more over the next few days.

[thetomester13]

@atrilahiji I came across a few things, wondering if you have some input on these:

• I'm not able to simply 'run' workflows. Trying to 'Execute' results in an endless spinning of a wheel. When trying to hit 'Stop' to stop the execution, this shows up in the logs:

Apr 27 13:51:02 Error: The execution id "6" could not be found.
Apr 27 13:51:02 at /usr/local/node-12.16.3/lib/node_modules/n8n/dist/src/Server.js:1142:27
Apr 27 13:51:02 at runMicrotasks (<anonymous>)
Apr 27 13:51:02 at processTicksAndRejections (internal/process/task_queues.js:97:5)
Apr 27 13:51:02 at async /usr/local/node-12.16.3/lib/node_modules/n8n/dist/src/ResponseHelper.js:76:26

• I can switch over a workflow to a webhook, and then properly trigger the workflow, which is awesome! However, to test this out, I'm doing a simple 'send email' using my Cloudron SMTP credentials. This node fails on the workflow with the following error: ERROR: 140532647925632:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

I know this is very much a work in progress, just wanted to record these in case anyone has some input.

[A Former User]

@thetomester13 huh openssl errors??? O_O

Yeah not immediately sure why but I'll do some digging.

I'm also just going to do some cleaning up of the package

[thetomester13]

@atrilahiji upon further investigation , it seems as if it's just a problem with the Send Email node (or maybe my credentials? Though IMAP is confirmed working). I'm able to create other workflows with other triggers that run properly! Very awesome stuff!

[A Former User]

@thetomester13 Yeah seems to be a weird upstream issue. I also just disabled SSL for SMTP and it worked. Still using port 587

[A Former User]

@thetomester13 I also bumped both the N8N and Node versions

[girish]

@thetomester13 said in Sponsoring: n8n:

@atrilahiji upon further investigation , it seems as if it's just a problem with the Send Email node (or maybe my credentials? Though IMAP is confirmed working). I'm able to create other workflows with other triggers that run properly! Very awesome stuff!

There seems to a bug with the cert renewal logic which I am just investigating. If you go to Services -> Mail -> Restart it copies over the fresh cert.

[girish]

@atrilahiji @thetomester13 so, should i just go ahead and push that as unstable?

[thetomester13]

@atrilahiji said in Sponsoring: n8n:

@thetomester13 I also bumped both the N8N and Node versions

I'm still not able to get my SMTP Send Email node to work for some reason, even with the refresh of Mail certs and Ignoring SSL Errors. shrug not a huge deal for now, I'll play around with it some more coming up.

@girish said in Sponsoring: n8n:

@atrilahiji @thetomester13 so, should i just go ahead and push that as unstable?

I think that should be fine!

[A Former User]

@girish It seems stable enough to be unstable. FYI the most up to date package is here https://git.atrilahiji.dev/atrilahiji/cloudron-n8n-app

[thetomester13]

@atrilahiji ooooookay. You said you turned off SSL, not SSL Errors. Yes, turning that off in the credentials themselves worked!

[A Former User]

@thetomester13 Yep! Gmail seemed to think it was secured with TLS anyways so IDK? IMAP seems to work anyways.

[girish]

@atrilahiji do you think you can add a LICENSE file and I can then put the repo in git.cloudron.io. Thanks!

[A Former User]

@girish Done

[girish]

@atrilahiji Thanks! Here - https://git.cloudron.io/cloudron/n8n-app . you and @thetomester13 should have push access. I am just building the unstable package.

[girish]

OK, this is published as unstable now. I haven't really looked into the package code itself but I will take a look when I find the time this week. I created a n8n app category, so please continue discussing there.