Publishing community templates to the n8n library: what the review actually asks for
The n8n template library is one of the few places where a self-hosted automation builder can publish something for free and get real traffic from it. It is also a gatekept library: every submission is reviewed by a human, and the guidelines are stricter than the form suggests. We have submitted templates from a self-hosted instance, and this is the checklist we work from — what the review…
The n8n template library provides a platform where self-hosted automation builders can publish templates for free and gain visibility. However, submissions are carefully reviewed, following a strict checklist. The submission process occurs at creators.n8n.io, not within the n8n app. A creator account must be registered, verified via email, and from there templates can be submitted.
One important rule is that new authors can only have one template under review at a time. Once a template is approved or the reviewer sends it back, the button to submit the next template becomes disabled. This means that authors must plan and polish their templates one at a time, waiting for review before moving on to the next one. The first submission is particularly important, as a rejection means starting the review cycle over again.
Titles follow a specific format: action verb + object + where or from. This formula is not just a style preference, but a review criterion. The title must accurately describe the action performed by the workflow, using concrete service names rather than vague or hype terms. Titles cannot include emojis or marketing buzzwords.
Descriptions for each template are required and should be 200 words of English markdown, divided into sections. The description should explain who the template is for, how it works step by step, how to set it up, what is needed, and how to extend it. Markdown formatting is allowed, but the description must render correctly in n8n's library renderer, unlike GitHub READMEs which handle nested tables and raw HTML better.
Importantly, sticky notes in the workflow are mandatory and cannot be omitted. These notes serve as documentation for the workflow, explaining each step in detail.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.