Discuss GitHub issues with council-style AI reviewers and optional BVC
Ready for 3.0What this workflow does
This workflow has 79 nodes and runs when someone submits an n8n form (“Let AI reviewers discuss a bug”) (plus 1 other trigger). It uses only n8n's built-in nodes.
How it runs
Trigger: When someone submits an n8n form (“Let AI reviewers discuss a bug”) (plus 1 other trigger).
- Configure approved input (Edit Fields (Set)): sets or maps fields
- Validate configuration (Code): runs custom JavaScript code
- Ready to read issue? (If): checks a condition and branches into true / false
- Prepare issue URL (Code): runs custom JavaScript code
- Final report (Code): runs custom JavaScript code
- GitHub issue (HTTP Request): calls an HTTP API (GET)
- Show result in form? (If): checks a condition and branches into true / false
- Validate issue (Code): runs custom JavaScript code
- Your discussion result (n8n Form): shows the next form page
- Ready to read commit? (If): checks a condition and branches into true / false
…plus 67 more steps. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Manual Trigger
n8n-nodes-base.manualTrigger - Edit Fields (Set)
n8n-nodes-base.set - n8n Form Trigger
n8n-nodes-base.formTrigger - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - n8n Form
n8n-nodes-base.form
From the author
Quick overview Get a proposed fix for a GitHub issue from four independent AI reviewer roles. Choose your model provider during setup. Optional BVC decides whether another discussion round is worthwhile within a fixed call limit. A person reviews the…