Add Author & Licence Properties to n8n Template JSON Schema

Feature Requests
1

The idea is:

To allow optional attribution and explicit licence grants of N8N templates shared publicly. The proposal is to introduce and standardise 2 new properties in the official n8n templates json schema.

{
  "author": {
    "type": "string",
    "description": "ie. Jim Le <[email protected]> (https://jimle.uk)"
  },
  "licence": {
    "type": "string",
    "description": "ie. BSD-3-Clause"
  },
  ...
}

My use case:

As an n8n creator, I would like the option to be explicit on what licence I publish my templates in the template gallery. This is to ensure users of my templates are informed about what terms/liabilities they agree to when using my work and where appropriate, mitigate any legal compliance risks or misunderstanding later down the line.

On the other side, liability disclaimers included in the licence would also serve to protect me as the author should the damages or loss occur using my template (very unlikely but still!).

I think it would be beneficial to add this because:

(Disclaimer: I used ChatGPT to list the following but I totally agree!)

  • Encourages Attribution and Recognition
    Adding author information promotes recognition for creators, encouraging more community contributions by giving credit where it’s due.
  • Improves Legal Clarity
    Including a licence field helps clarify the legal terms of use and redistribution, reducing uncertainty and potential IP issues when reusing templates.
  • Fosters a Culture of Openness and Professionalism
    These fields align with open-source best practices, helping n8n establish itself as a responsible platform that values transparency and ethical sharing.
  • Enables Better Community Connections
    With author details available, users can reach out for collaboration, questions, or consulting—strengthening the developer ecosystem around n8n.
  • Future-Proofs the Template System
    Standardizing metadata like author and licence now lays a solid foundation for future enhancements, like template directories, search filters, or attribution in UIs.

Any resources to support this?

Many examples to learn from

Are you willing to work on this?

I’m happy to gather community feedback and promote this!

Credit

2

Excellent @Jim_Le !

2 Likes