-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
n8n integration #21286
Comments
That would actually make sense to implement. I have no idea how complicated it could be, but if you run Gitea within a more complex organization, you could implement complex automation tasks with almost no effort on Gitea's end. |
Merging into: #1089 |
not sure this is solved by that, as a proper n8n integration also adds some nodes on their side I think, but I have not gotten around to using it yet |
Well, the primary problem I can see (which probably also confused @techknowlogick) : |
I did had a quic look into there youtube channel, for my understanding it is #1089 on our side, the rest n8n has to program on there site (mostly to by using the existing rest api) |
Feature Description
n8n is essentially a self-hostable IFTTT/Zapier alternative
See also https://kolaente.dev/vikunja/api/issues/1249#issuecomment-36094
n8n already has integrations for discourse, zulip, invoiceninja, zammad and many more - by tapping into its ecosystem gitea can be integrated much more easily with other open-source tools (and even non-FOSS tools) for a coherent user experience.
Even imports from Github or other forges might be realised over that in the future, so that you don't need to keep creating specific connections but use their abstraction layer.
Screenshots
No response
The text was updated successfully, but these errors were encountered: