Hey builders!
I’m Miquel, the creator of n8nhackers and I want to personally invite you to our private (but free) Telegram group.
This group is for anyone passionate about n8n who wants to stay updated, discover new workflows, and connect with a community that’s all about automating smarter.
Inside the channel, you’ll find:
-
Latest n8n Releases: Be the first to know about new features and improvements.
-
Community Discussions: Get real-time updates on new topics and solutions from the official community.
-
Job Opportunities: Find n8n-related jobs and projects.
-
Workflow Templates: Discover ready-to-use official templates to speed up your automations daily.
-
Community Nodes: Stay updated on new nodes created by the community.
And more secrets that I am cooking for the community 
If you’re into n8n, this is the place you want to be.
It’s private, but free. Just automation-focused people like you and me.
Join here: n8nhackers Telegram Channel
See all info here n8nhackers Announcement
Let’s build something great together 
PS: I use n8n powered with ai and Python to feed the group properly 
3 Likes
Hi, nice initiative. Maybe something nice to do would be some form of Hackathon. Choose some actual problem statement / fun problem and have a (collaborative) go at it.
Reg
J.
1 Like
Completely agree @jcuypers
Community is the core of n8n 
Do you have any ideas?
Well, I could think of something a few times but why not turn the first hackaton in something like (so we don’t have to think too much and it becomes a challenge):
Generate a workflow that generates 3 to 5 ideas around workflow automation. Emphasize on technology X/domain X (per month it changes). Generate a short believable use case for each one with clear starting point and end result
After that generate a poll based on the ideas and gather results as well as potentials comments.
reg,
J.
1 Like
Find a sponsor: @n8n? (you can never have enough t-shirts)
1 Like
That sounds awesome, @jcuypers
Totally — I’ve got my own n8n T-shirt already, so no conflict of interest! 
1 Like
Well obviously there need to be published solution requirements and what the solution will be marked against
Cost / performance / novelty Each time new impartial (AI) jury
I’m all for fairness and giving t-shirts to the right people
Reg
J.
1 Like
Absolutely.
Some quick ideas that are burning my head:
- Quarterly hackathons (every 3 months)
- One clear theme per hackathon (rotating topics like AI, eCommerce, APIs, etc.)
- Individual participation only (no teams for now)
I think this way we can keep it simple, focused, and make each hackathon feel special.
Curious to hear your thoughts!
1 Like
Sounds good. the only problem with the “individual” participation is that there is already a potential divide between participants.
- knowledge divide(someone with 4 years on N8N obviously has an advantage)
- resource divide: if for 4 years you created templates you surely have already something that matches 50% the requirements
- many other points… If there are more, chances are they would respect the rules better. hoping there is at least one with a conscience
Anyway, nothing is perfect. I would propose something like Kaggle competitions: individual or teaming up with other (up to 3 people) this gives newbies a chance and also to learn. in essence, this team part is invisible to the organisor. their own risk/schedule/etc. hackaton are also usually built on this team idea anyways.
thats my 2 cents.
BTW the clear upfront themes is a good thing, so people can easily plan and opt-out. e,g. social media stuff doesn’t interest me at all.
reg,
J.
1 Like
Good points — totally agree!
The knowledge and resource gap is real, and teaming could definitely help balance that out.
I like the idea of keeping it flexible like Kaggle competitions: people can participate individually or team up (up to 3 people max).
We don’t have to over-manage the teams either — just let them self-organize if they want, and submit together under one name.
Sounds like a fair way to make it more inclusive and give newbies a real chance too.
Your two cents are mine as well! Let’s integrate that into the plan.
Updated Hackathon Format:
- Hackathon every 3 months (quarterly)
- One specific theme per hackathon (rotating domains/technologies)
- Participation: Individual/Teams of up to 3 people (self-organized)
- Judge: half human / half ai
1 Like
Let’s start with full human jury (3 people which don’t have skin in the game) and see if we can add AI as like aid (something like soccer VAR).
I doubt whether the AI will be able to extract the essence of the workflow solutions into a score. Sometimes it’s good to keep our imaginations in check…
Reg
J.
1 Like
Final decision must be human, obviously.
AI could score basic data about flows (like complexity, scaling up, best practices, and so on).
That’s an small sample about best practices that we do when documenting a workflow at n8nhackers.com:
1 Like
