HumationHuman + Automation
Back to Catalog

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

totomatotoma
61 views
2/3/2026
Data IngestionMongoDBWebhookDatabaseAPI
Official Page

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.)

n8n Workflow: Curate Contributor-Friendly Issues with AI and Send GitHub Newsletter via Email

This n8n workflow leverages AI to identify and curate contributor-friendly issues from GitHub repositories, then compiles them into an email newsletter for easy distribution. It streamlines the process of finding good first issues and communicating them to potential contributors.

What it does

This workflow automates the following steps:

  1. Manually Triggered: The workflow is initiated manually, allowing for on-demand curation and newsletter generation.
  2. AI Agent for Issue Curation: An AI Agent (powered by LangChain) interacts with GitHub via an MCP Client Tool to fetch and process issues.
  3. Structured Output Parsing: The AI Agent's output is parsed into a structured format, likely extracting key details about the identified issues.
  4. Issue Filtering (Conditional Logic): The workflow includes an "If" node, suggesting that issues are filtered based on certain criteria (e.g., "good first issue" labels, complexity, or other AI-determined attributes).
  5. Data Transformation (Code): A "Code" node is used to perform custom JavaScript logic, likely to format the curated issues or prepare the email content.
  6. Issue Splitting: The "Split Out" node processes the filtered and transformed issues, potentially to handle each issue individually for further processing or email content generation.
  7. Data Merging: A "Merge" node combines data from different branches of the workflow, likely bringing together the curated issue details and any additional information needed for the newsletter.
  8. HTTP Request (Optional/External API Interaction): An HTTP Request node is present, which could be used for various purposes such as interacting with a GitHub API (beyond the GraphQL node), a custom backend, or another service.
  9. Email Newsletter Generation and Sending: Finally, the "Send Email" node compiles and dispatches the curated issues as an email newsletter to a specified recipient list.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • GitHub Account: Access to GitHub repositories from which issues will be curated.
  • OpenRouter Chat Model: An OpenRouter API key and configuration for the OpenRouter Chat Model node to power the AI Agent.
  • LangChain AI Agent: The n8n LangChain nodes installed and configured.
  • MCP Client Tool: The n8n LangChain MCP Client Tool node configured to interact with GitHub or other relevant services.
  • SMTP Email Credentials: Configured SMTP credentials in n8n for sending emails.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Credentials:
    • Set up your OpenRouter Chat Model credentials.
    • Configure your SMTP Email credentials.
    • Ensure the MCP Client Tool is correctly configured to interact with your GitHub account or the necessary API endpoints.
  3. Customize AI Agent: Review and adjust the AI Agent node's prompt and tools to precisely define how it identifies "contributor-friendly" issues.
  4. Adjust Filtering Logic: Modify the If node's conditions to refine what constitutes a "contributor-friendly" issue based on your specific criteria.
  5. Update Code Node: Customize the Code node if you need specific data transformations or formatting for the issues before they are sent in the email.
  6. Configure Email Details: In the Send Email node, specify the recipient email addresses, subject line, and customize the email body template to present the curated issues effectively.
  7. Execute Workflow: Click "Execute Workflow" to run the process manually and send out the newsletter.

Related Templates

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247

Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review

This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.

gotoHumanBy gotoHuman
353

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616