Community Contributions Playbook

Welcome to the n8n community! This playbook will guide you through the different ways you can contribute to making n8n better for everyone. The focus of this Playbook is on triaging issues, which helps our engineers focus on fixing issues and implementing features faster.

Please check out the guide below to gain a better idea at what it is the Community Contributors do and how to register if interested.

</aside>

Getting Started

Start small: Begin with triaging issues or reproducing simple bugs
Comment before working: Let others know you're working on an issue to avoid duplication
Watch the repository: Stay updated on new issues and discussions

How to contribute

Triaging GitHub Issues and Answering Questions

Help maintain a healthy issue tracker by organising and responding to GitHub issues. Look for GitHub issues labeled #triage:pending.

Finding issues to help with:

Recent issues Past 7 days Issues
Overdue issues Overdue Issues

How to Triage Issues:

Ask clarifying questions or asking for additional information like n8n version, workflow details, or error messages (these prompts in the bug template, but sometimes they aren’t filled in)
Verify reproducibility by trying to reproduce the issue
Help categorising the issue by suggesting a label in the comments (you are not able to add labels directly to the issue, but our automation will pick up your comment)
Suggest closing resolved issues: If an issue has been fixed or is no longer relevant, suggest closing it. Please also inform the user why, we have a selection of pre-written comments and corresponding labels to help you with this

Best Practices for Responding to Issues:

Be welcoming and patient, especially with new users
Use clear language - avoid abbreviations, slang or terms new users might not know.