💅 Example Great Workflow Templates

Below are examples of approved templates that meet our submission guidelines

• https://n8n.io/workflows/2109-enrich-new-discourse-members-with-clearbit-then-notify-in-slack/
• https://n8n.io/workflows/2116-verify-emails-and-enrich-new-form-leads-and-save-them-to-hubspot/

☑️ Guidelines

<aside> 📣 tl;dr: make sure the template is relevant to a broad enough group, well annotated so it’s clear what it does, and has some clear set up steps (via sticky, video, notion doc etc)

</aside>

• All your content should be written in English and spelled correctly

• Provide a detailed description: Provide a concise and informative description outlining the template's functionality and expected outcomes. Include a brief setup guide for user convenience. A detailed description not only clarifies the template's purpose but also enhances its discoverability through SEO. It’s advised to use these sections in your description:

  • Who is this for?
  • What problem is this workflow solving? / use case
  • What this workflow does
  • Setup
  • How to customize this workflow to your needs

• Optimize for SEO:

  1. Use the main nodes in the title and use sentence-style capitalization, e.g. One-way sync between Pipedrive and HubSpot or Create an invoice in Google Sheets based on Typeform submission
  2. Try to have a description with ~ 300 words
  3. Use H2 and H3 headers to structure your description into sections

• Rename your workflow’s nodes to explain what that step is doing. Workflow notes are a handy feature as are Sticky notes.

• Add a Sticky note that explains what the template does and any dependencies required.
  • If you have an external setup guide, like a notion page, link it here too.
  • You are a rockstar if you also make a quick setup video 👩‍🎤. Loom recordings are a simple way to go. You don’t have to be a pro Youtuber, simple videos are still really helpful. Plus our community will really appreciate it 🥰
  • Use different sticky colors

Always include a sticky note that explains the workflow

• Templates need to work across all deployment types of n8n, including n8n cloud (that also means that we don’t accept templates including community nodes for now)
• Try to make templates relevant to one of our categories.
  • Template categories (as of 15NOV2023)
• Your template should cover a real use case of a potential user. Consider how to make the template applicable to a broader audience by finding the right balance in generalizing your use case.

<aside> 🧑‍🍳 #tip: Action verb thing being manipulated to/ on / in / from where

</aside>

• Avoid using custom nodes, community nodes, or custom modules in your workflow or Code node. We intend to enhance the user experience to better accommodate these elements. However, incorporating them in your template now may limit the number of users who can successfully set up your template.

👍 Additional Tips

• Try to use an edit fields node that allows users to set all their variables in one node
• Try to empathize with a user who is attempting to use your template. Keep in mind that they may not know as much about n8n as you do.