HumationHuman + Automation
Back to Catalog

GitHub bounty issue tracker & alert system (Google Sheets + Email/WhatsApp)

Jeffrey W.Jeffrey W.
146 views
2/3/2026
Data ProcessingAuthenticationToken ManagementHTTP RequestAPI
Official Page

GitHub Bounty Issue Tracker & Alert System (Google Sheets + Email/WhatsApp)

Overview

Looking for a way to track GitHub bounty issues automatically and get notified in real time? This GitHub Bounty Tracker workflow monitors repositories for issues labeled 💎 Bounty, logs them in Google Sheets, and sends instant alerts via Email (HTML-styled) or WhatsApp. Perfect for developers, freelancers, and open-source contributors who want to discover and claim paid opportunities faster.

What This Workflow Does

🔎 Automated Bounty Discovery

  • Searches GitHub hourly for all open issues labeled with “💎 Bounty.”
  • Filters duplicates to avoid re-tracking the same issue.

📢 Smart Notifications

  • Sends styled HTML email alerts with GitHub-themed design.
  • WhatsApp Business API integration (optional, disabled by default).
  • Alerts only for bounties created within the last 5 days.

📊 Google Sheets Tracking

  • Sheet1: Complete bounty list (all tracked issues).
  • Sheet2: Recent notification log (for quick reference).

🔄 Status Updates

  • Checks every 6 hours for issue changes (open/closed state, new comments).
  • Includes bounty amount, issue details, and direct GitHub links.

Use Cases

  • 👩‍💻 Freelance developers hunting for paid open-source work.
  • 🛠 Development teams tracking bounty opportunities for their stack.
  • 🌍 Community managers monitoring open-source bounty program engagement.
  • 🤝 Open-source contributors looking for compensated tasks.

Requirements

  • GitHub Personal Access Token (with repo access).
  • Google Sheets (2 sheets required: Sheet1 = bounties, Sheet2 = notifications).
  • Gmail account (OAuth2 for sending email alerts).
  • WhatsApp Business API credentials (optional).

Configuration Notes

This workflow supports pagination for large result sets and includes filters to prevent duplicate notifications.
You can customize the GitHub search query in the HTTP Request node to target:

  • Specific repositories
  • Custom labels
  • Team/organization projects

Frequently Asked Questions (FAQ)

Q: How often will I get notifications?
A: By default, new bounties trigger alerts once an hour. Updates on existing issues (status/comments) are checked every 6 hours.

Q: Do I need WhatsApp integration?
A: No, it’s optional. Email alerts work out-of-the-box.

Q: Can I filter by bounty amount?
A: Yes, the workflow extracts bounty details and you can add filters in your Google Sheets or notification logic.

Why Use This GitHub Bounty Tracker?

Unlike manual searches, this workflow ensures you never miss a paid GitHub issue. Whether you’re a freelancer looking for income, a team seeking funded tasks, or a contributor wanting recognition and rewards, this system keeps you updated automatically.

n8n GitHub Bounty Issue Tracker & Alert System

This n8n workflow automates the process of tracking GitHub issues, extracting key information, and sending alerts via email and WhatsApp. It's designed to help teams monitor specific GitHub repositories for new issues, especially those related to bounties or critical tasks, and ensure timely notifications.

What it does

This workflow performs the following key steps:

  1. Scheduled Trigger: The workflow is initiated on a regular schedule (e.g., daily, hourly) to check for updates.
  2. Fetch GitHub Issues: It makes an HTTP request to the GitHub API to retrieve a list of issues from a specified repository.
  3. Extract Data: The HTML node is used to parse the response from the GitHub API, likely extracting issue titles, URLs, and other relevant details.
  4. Split Issues: The Split Out node separates the retrieved issues into individual items, allowing for individual processing.
  5. Filter Issues: A Filter node applies logic to determine which issues are relevant for further processing (e.g., filtering by labels like "bounty", "critical", or specific keywords).
  6. Update Google Sheets: For each filtered issue, it adds a new row to a Google Sheet, logging the issue details. This creates a centralized tracker for all relevant issues.
  7. Merge Data: The Merge node combines the output from the Google Sheets operation.
  8. Send Email Alert: It sends an email notification via Gmail with details of the new or updated issues.
  9. Send WhatsApp Alert: It sends a WhatsApp message via WhatsApp Business Cloud, providing a quick alert about the issues.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running instance of n8n.
  • GitHub Account: Access to a GitHub repository (public or private with appropriate authentication).
  • Google Sheets Account: A Google Sheets spreadsheet set up to log issue details.
  • Gmail Account: A Gmail account for sending email alerts.
  • WhatsApp Business Cloud Account: A configured WhatsApp Business Cloud account for sending WhatsApp alerts.

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • HTTP Request (GitHub): You might need to set up an API key or personal access token for GitHub if accessing private repositories or to avoid rate limits.
    • Google Sheets: Configure your Google Sheets OAuth2 credentials. Select the correct spreadsheet and sheet name in the node settings.
    • Gmail: Configure your Gmail OAuth2 credentials.
    • WhatsApp Business Cloud: Configure your WhatsApp Business Cloud credentials.
  3. Customize Nodes:
    • Schedule Trigger: Adjust the schedule to your desired frequency (e.g., every 15 minutes, once a day).
    • HTTP Request: Update the URL to point to your specific GitHub repository's issues API endpoint (e.g., https://api.github.com/repos/YOUR_ORG/YOUR_REPO/issues).
    • HTML: Review and adjust the CSS selectors in the HTML node to correctly extract data from GitHub's API response.
    • Filter: Modify the filter conditions to match your specific criteria for issues (e.g., item.labels.includes('bounty'), item.title.includes('critical')).
    • Google Sheets: Ensure the column mapping in the Google Sheets node matches your spreadsheet's headers.
    • Gmail: Customize the email subject and body to include relevant issue details using expressions. Set the recipient email address.
    • WhatsApp Business Cloud: Customize the message template and recipient phone number.
  4. Activate the Workflow: Once configured, activate the workflow to start monitoring and alerting.

Related Templates

Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution

AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) 🧠 AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative — all powered by AI logic, sir. --- 💡 Key Advantages ⚡ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. 🧠 AI Qualification Engine An OpenAI-powered Agent evaluates the lead’s industry, region, and needs to generate a persona summary and routing rationale. 📊 Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. 💬 Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. 🔁 Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- ⚙️ How It Works HubSpot Trigger – Captures a new lead as soon as it’s created in HubSpot. Fetch Contact Data – Retrieves all relevant fields like name, company, and industry. Clean & Format Data – A Code node standardizes and structures the data for consistency. Airtable Record Creation – Logs the lead data into the “Leads” table for centralized tracking. AI Agent Qualification – The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update – Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification – Sends a real-time message tagging the rep with lead info. Gmail Notification – Sends a personalized handoff email with context and follow-up actions. HubSpot Sync – Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- 🛠️ Setup Steps Trigger Node: HubSpot → Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the “Leads” table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- 🔐 Credentials Required HubSpot OAuth2 API – To fetch and update leads. Airtable Personal Access Token – To store and update lead data. OpenAI API – To power the AI qualification and matching logic. Slack OAuth2 – For sending team notifications. Gmail OAuth2 – For automatic email alerts to assigned reps, sir. --- 👤 Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- 💬 Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular — perfect for scaling across global sales teams, sir.

MANISH KUMARBy MANISH KUMAR
113

Track daily moods with AI analysis & reports using GPT-4o, Data Tables & Gmail

Track your daily mood in one tap and receive automated AI summaries of your emotional trends every week and month. Perfect for self-reflection, wellness tracking, or personal analytics. This workflow logs moods sent through a webhook (/mood) into Data Tables, analyzes them weekly and monthly with OpenAI (GPT-4o), and emails you clear summaries and actionable recommendations via Gmail. ⚙️ How It Works Webhook – Mood → Collects new entries (🙂, 😐, or 😩) plus an optional note. Set Mood Data → Adds date, hour, and note fields automatically. Insert Mood Row → Stores each record in a Data Table. Weekly Schedule (Sunday 20:00) → Aggregates the last 7 days and sends a summarized report. Monthly Schedule (Day 1 at 08:00) → Aggregates the last 30 days for a deeper AI analysis. OpenAI Analysis → Generates insights, patterns, and 3 actionable recommendations. Gmail → Sends the full report (chart + AI text) to your inbox. 📊 Example Auto-Email Weekly Mood Summary (last 7 days) 🙂 5 ██████████ 😐 2 ████ 😩 0 Average: 1.7 (Positive 🙂) AI Insights: You’re trending upward this week — notes show that exercise days improved mood. Try keeping short walks mid-week to stabilize energy. 🧩 Requirements n8n Data Tables enabled OpenAI credential (GPT-4o or GPT-4 Turbo) Gmail OAuth2 credential to send summaries 🔧 Setup Instructions Connect your credentials: Add your own OpenAI and Gmail OAuth2 credentials. Set your Data Table ID: Open the Insert Mood Row node and enter your own Data Table ID. Without this, new moods won’t be stored. Replace the email placeholder: In the Gmail nodes, replace your.email@example.com with your actual address. Deploy and run: Send a test POST request to /mood (e.g. { "mood": "🙂", "note": "productive day" }) to log your first entry. ⚠️ Before activating the workflow, ensure you have configured the Data Table ID in the “Insert Mood Row” node. 🧠 AI Analysis Interprets mood patterns using GPT-4o. Highlights trends, potential triggers, and suggests 3 specific actions. Runs automatically every week and month. 🔒 Security No personal data is exposed outside your n8n instance. Always remove or anonymize credential references before sharing publicly. 💡 Ideal For Personal mood journaling and AI feedback Therapists tracking client progress Productivity or self-quantification projects 🗒️ Sticky Notes Guide 🟡 Mood Logging Webhook POST /mood receives mood + optional note. ⚠️ Configure your own Data Table ID in the “Insert Mood Row” node before running. 🟢 Weekly Summary Runs every Sunday 20:00 → aggregates last 7 days → generates AI insights + emails report. 🔵 Monthly Summary Runs on Day 1 at 08:00 → aggregates last 30 days → creates monthly reflection. 🟣 AI Analysis Uses OpenAI GPT-4o to interpret trends and recommend actions. 🟠 Email Delivery Sends formatted summaries to your inbox automatically.

Jose CastilloBy Jose Castillo
105

IT ops AI SlackBot workflow - chat with your knowledge base

Video Demo: Click here to see a video of this workflow in action. Summary Description: The "IT Department Q&A Workflow" is designed to streamline and automate the process of handling IT-related inquiries from employees through Slack. When an employee sends a direct message (DM) to the IT department's Slack channel, the workflow is triggered. The initial step involves the "Receive DMs" node, which listens for new messages. Upon receiving a message, the workflow verifies the webhook by responding to Slack's challenge request, ensuring that the communication channel is active and secure. Once the webhook is verified, the workflow checks if the message sender is a bot using the "Check if Bot" node. If the sender is identified as a bot, the workflow terminates the process to avoid unnecessary actions. If the sender is a human, the workflow sends an acknowledgment message back to the user, confirming that their query is being processed. This is achieved through the "Send Initial Message" node, which posts a simple message like "On it!" to the user's Slack channel. The core functionality of the workflow is powered by the "AI Agent" node, which utilizes the OpenAI GPT-4 model to interpret and respond to the user's query. This AI-driven node processes the text of the received message, generating an appropriate response based on the context and information available. To maintain conversation context, the "Window Buffer Memory" node stores the last five messages from each user, ensuring that the AI agent can provide coherent and contextually relevant answers. Additionally, the workflow includes a custom Knowledge Base (KB) tool (see that tool template here) that integrates with the AI agent, allowing it to search the company's internal KB for relevant information. After generating the response, the workflow cleans up the initial acknowledgment message using the "Delete Initial Message" node to keep the conversation thread clean. Finally, the generated response is sent back to the user via the "Send Message" node, providing them with the information or assistance they requested. This workflow effectively automates the IT support process, reducing response times and improving efficiency. To quickly deploy the Knowledge Ninja app in Slack, use the app manifest below and don't forget to replace the two sample urls: { "display_information": { "name": "Knowledge Ninja", "description": "IT Department Q&A Workflow", "background_color": "005e5e" }, "features": { "bot_user": { "display_name": "IT Ops AI SlackBot Workflow", "always_online": true } }, "oauth_config": { "redirect_urls": [ "Replace everything inside the double quotes with your slack redirect oauth url, for example: https://n8n.domain.com/rest/oauth2-credential/callback" ], "scopes": { "user": [ "search:read" ], "bot": [ "chat:write", "chat:write.customize", "groups:history", "groups:read", "groups:write", "groups:write.invites", "groups:write.topic", "im:history", "im:read", "im:write", "mpim:history", "mpim:read", "mpim:write", "mpim:write.topic", "usergroups:read", "usergroups:write", "users:write", "channels:history" ] } }, "settings": { "event_subscriptions": { "request_url": "Replace everything inside the double quotes with your workflow webhook url, for example: https://n8n.domain.com/webhook/99db3e73-57d8-4107-ab02-5b7e713894ad", "bot_events": [ "message.im" ] }, "orgdeployenabled": false, "socketmodeenabled": false, "tokenrotationenabled": false } }

Angel MenendezBy Angel Menendez
39013