My First n8n Template Was Rejected Twice

The second rejection email arrived and I sat staring at it for a while.

I had ten automations running in production. Stable, handling real work every day, not slipping. Sharing them felt obvious — keeping something useful locked to my own setup is a waste.

So I submitted one to the n8n template library. I was confident. It already worked in the real world, so I assumed the review was a formality.

It came back rejected. No explanatory sticky notes. Templates get read by strangers, and mine explained nothing about how it worked. Fair enough.

I added them and resubmitted.

Rejected again. This time the sticky text was overlapping the nodes, so half of what I had written was sitting behind the node boxes where nobody could read it.

That one stung more. You build something, rely on it for months, and get told twice it is not ready to hand to anyone else.

But neither rejection was about the automation. Both were about the explanation. Working code and explained code are two different pieces of work, and I had only done the first one.

Third submission: accepted.

https://n8n.io/creators/shivamg11