Hi all, I’m Niv from the product team at n8n, and you’re going to see me more often around here, mostly asking you questions about your experience with n8n
In the past couple of months, we have dedicated extra resources to address your contributions on our GitHub repository. We could have definitely done better in the past, with many open PRs sitting in the repository for a long while. However, we really value all your contributions, want to do better on this front, and we don’t want you to wait for extended periods of time.
I’m happy to say that we have recently merged more than 30 PRs into our product, and the same amount is in internal review as we speak. On the same note, we had to push back on 15 contributions for several reasons. This was mostly due to mismatches with our direction, and some features that would be redundant once some of the upcoming features were released.
For the sake of prioritisation, and aligned efforts, both from your side and ours, we’d like to share with you two of the upcoming features that we are planning to release soon. Both with the aim to make the path to a meaningful usage n8n easier:
Contributors will be able to publish their custom nodes via npmjs.com, and users will be able to load them into their instance with a simple and clean UI. We can’t wait to see what you have developed and how it would be used by you!
- What does it mean for your new node contributions? Once this feature is tested and released, we would kindly ask all of you who have submitted such a PR (new node), to just upload it to the repository.
When a native app node lacks an operation, it can be cumbersome to recreate that credential in the HTTP Request node and make a generic call - we feel your pain! So we’re planning to introduce an easier way to connect services (that already have a node in n8n) via the HTTP Request node.
Needless to say that bug fixes, nodes, and product improvement are always very very welcomed!
Thank you for your support and we can’t wait to see what you are coming up with!