Skip to main content

Curate contributor-friendly issues with AI and send GitHub newsletter via email

Workflow preview

Workflow preview
100%
Curate contributor-friendly issues with AI and send GitHub newsletter via email preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Use Cases Receive a newsletter featuring curated, contributor friendly issues from your favorite repositories. By regularly reviewing active issues and new releases, you'll naturally develop strong...

Best for

  • Social Media automation workflows
  • AI RAG automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.code, n8n-nodes-base.graphql, n8n-nodes-base.splitout, n8n-nodes-base.merge, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.lmchatopenrouter, @n8n/n8n-nodes-langchain.mcpclienttool

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by totoma.

Original n8n.io source

1.1 Workflow description

Title
Curate contributor-friendly issues with AI and send GitHub newsletter via email
Workflow name
Curate contributor-friendly issues with AI and send GitHub newsletter via email

Use Cases

Receive a newsletter featuring curated, contributor-friendly issues from your favorite repositories.

By regularly reviewing active issues and new releases, you'll naturally develop stronger habits around open source contribution as your brain starts recognizing these projects as important.

How It Works

  • Collects the latest issues, comments, and recent commits using the GitHub API.
  • Uses an AI model to select up to three beginner-friendly issues worth contributing to.
  • Summarizes each issue—with contribution guidance and relevance insights—using Deepwiki MCP.
  • Converts the summaries into HTML and delivers them as an email newsletter.

Requirements

How to Use

  1. Update the “Load repo info” node with your target repository’s owner and name (e.g. owner: vercel, repo: next.js).
  2. Add your GitHub Personal Access Token to the credentials of the “Get Issues from GitHub” node.
  3. Connect your OpenRouter API key to all models linked to the Agent node.
  4. Add your Google App Password to the “Send Email” node credentials.
  5. Enter the same email address (associated with the Google App Password) in both the “to email” and “from email” fields — the newsletter will be sent to this address.

Customization

  • Adjust the maximum number of contributor-friendly issues retrieved in the “Get Top Fit Issues” node.
  • Improve results by tuning the models connected to the Agent node.
  • Refine the criteria for “contributor-friendliness” within the “IssueRank Agent” node.

Cron Setup

  • Replace the manual trigger with a Schedule Trigger node or another scheduling-capable node.
  • If you don't have an n8n Cloud account, use this alternative setup: fork the repository and follow the setup instructions.

TroubleShooting

  • If there is an issue with the AI model’s response, modify the ai_model setting. (If you want to use a free model, search for models containing “free” and choose one of them.)

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - When clicking ‘Execute workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Load Repo Info

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 3 - Get Issue From Github

Type / Role
n8n-nodes-base.graphql - graphql
Config choices
Version 1.1

Block 4 - Split Out

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 5 - get Top Fit Issues

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 6 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 7 - IssueRank Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3

Block 8 - IssueRank Fallback Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 9 - Deepwiki Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3

Block 10 - Deepwiki Main Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 11 - Deepwiki Fallback Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 12 - Deepwiki MCP

Type / Role
@n8n/n8n-nodes-langchain.mcpClientTool - mcpClientTool
Config choices
Version 1.2

Block 13 - IssueRank Structured Output Parser

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 14 - Deepwiki Structured Output Parser

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 15 - IssueRank Parser Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 16 - Deepwiki Parser Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 17 - Title Generator Agent

Type / Role
@n8n/n8n-nodes-langchain.agent - agent
Config choices
Version 3

Block 18 - Title Generator Main Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 19 - Title Generator Fallback Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenRouter - lmChatOpenRouter
Config choices
Version 1

Block 20 - Merge1

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 21 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Sticky Note6

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 23 - Sticky Note7

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 24 - Sticky Note8

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 34 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow Curate contributor-friendly issues with AI and send GitHub newsletter via email
Complexity advanced
Nodes 34
Categories Social Media, AI RAG
Author totoma
Published 06 Dec 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/11549/11549.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Curate contributor-friendly issues with AI and send GitHub newsletter via email do?

Use Cases Receive a newsletter featuring curated, contributor friendly issues from your favorite repositories. By regularly reviewing active issues and new releases, you'll naturally develop strong...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Social Media, AI RAG use case.