HumationHuman + Automation
Back to Catalog

Automate GitHub PRs & JIRA updates from Git commit commands-single repo

Intuz Intuz
705 views
2/3/2026
AIYouTubeOpenAISummarizationVideo
Official Page

This n8n template from Intuz delivers a complete and automated solution to streamline your development workflow for a single repository.

By embedding specific keywords and a JIRA issue ID within your git commit commands, this workflow automatically creates a Pull Request in GitHub and simultaneously updates the corresponding JIRA ticket. This provides a complete, seamless integration that eliminates manual steps and keeps your project management perfectly in sync with your codebase.

How it works

This workflow acts as a powerful bridge between your Git repository and your project management tools, driven entirely by the structure of your commit messages.

  1. GitHub Webhook Trigger: The workflow starts when a developer pushes a new commit to a specified repository in GitHub.

  2. Parse Commit Message: A Code node extracts key information from the commit message:

  • The JIRA Issue Key (e.g., FF-1196).
  • The base branch for the PR (e.g., development).
  • Action commands like [auto-pr] and [taskcompleted].
  1. Conditional PR Creation: An IF node checks if the [auto-pr] command is present.
  • If yes, it uses the GitHub node to automatically create a pull request from the developer's branch to the specified base branch.
  • If no, this step is skipped, allowing for multiple commits before a PR is made.
  1. Conditional JIRA Update: Another IF node checks for the [taskcompleted] command.
  • If yes, it uses the JIRA node to transition the corresponding issue to your "Done" status (e.g., "Task Completed" or "In Review").
  • If no, the JIRA issue remains in its current state, perfect for work-in-progress commits.

How to Use: Quick Start Guide

  1. Click the "Use Template" button to import this workflow into your n8n instance.

  2. Configure the GitHub Trigger:

  • Open the "GitHub Push Trigger" node. It will display a unique Webhook URL. Copy this URL.
  • In your GitHub repository, go to Settings > Webhooks > Add webhook.
  • Paste the URL into the Payload URL field.
  • Set the Content type to application/json.
  • Under "Which events would you like to trigger this webhook?", select Just the push event. Click Add webhook.
  1. Connect Your Accounts:
  • GitHub: Select your GitHub API credential in the "Create Pull Request" node.
  • JIRA : Select your JIRA API credential in the "Update JIRA Issue Status" node.
  1. Customize the JIRA Transition (Important):
  • Open the "Update JIRA Issue Status" node.
  • In the Transition parameter, you need to set the specific status you want to move the issue to (e.g., 'Done', 'Completed', 'In Review'). You can use the ID or the exact name of the transition from your JIRA project's workflow.
  1. Activate the Workflow: Save your changes and activate the workflow. You're ready to automate!

Example Commit Message:

git commit -m "FF-1196 Implement OAuth login [auto-pr,development,taskcompleted]"

Key Requirements to Use Template

  • An active n8n instance.
  • A GitHub account with repository admin permissions to create webhooks.
  • A JIRA Cloud account with permissions to update issues.
  • Developers who can follow the specified git commit message format.

Connect with us

  • Website: https://www.intuz.com/services
  • Email: getstarted@intuz.com
  • LinkedIn: https://www.linkedin.com/company/intuz
  • Get Started: https://n8n.partnerlinks.io/intuz

For Custom Worflow Automation

Click here- Get Started

GitHub Commit to Jira & PR Automation

This n8n workflow automates the process of creating GitHub Pull Requests and updating Jira issues based on specific keywords found in Git commit messages. It streamlines the development process by linking code changes directly to project management tasks and facilitating code reviews.

What it does

This workflow listens for new push events on a GitHub repository and performs the following actions:

  1. Triggers on GitHub Push: Automatically activates when a new commit is pushed to a monitored GitHub repository.
  2. Extracts Commit Message: Retrieves the commit message from the latest push event.
  3. Checks for Keywords: Uses a Code node to parse the commit message and identify specific keywords (e.g., "JIRA-", "PR-").
  4. Conditional Logic:
    • If a Jira issue key is found, it proceeds to update the corresponding Jira issue.
    • If a PR creation keyword is found, it initiates the creation of a new GitHub Pull Request.
  5. Updates Jira Issue (if applicable): If a Jira issue key is detected, it makes an HTTP request to the Jira API to update the issue (e.g., adding a comment, changing status).
  6. Creates GitHub Pull Request (if applicable): If a PR creation keyword is detected, it uses the GitHub API to create a new pull request with details from the commit.
  7. Handles Errors: If no relevant keywords are found, the workflow stops with an error, indicating that no action was taken.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • GitHub Account & Repository: A GitHub account and a repository where this workflow will listen for push events.
    • GitHub Credential: An n8n GitHub credential configured with appropriate permissions to read repository events and create pull requests.
    • GitHub Webhook: A webhook configured in your GitHub repository pointing to your n8n instance's webhook URL for the GitHub Trigger node.
  • Jira Account: A Jira account.
    • Jira Credential: An n8n Jira Software credential configured with permissions to update issues.
    • Jira API Token: You will likely need an API token for Jira authentication.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the three-dot menu in the top right and select "Import from JSON".
    • Paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • GitHub Trigger (Node ID: 17): Configure your GitHub credential. Ensure it has permissions to read repository events.
    • Jira Software (Node ID: 77): Configure your Jira Software credential. Ensure it has permissions to update issues.
    • HTTP Request (Node ID: 19): This node is likely used for interacting with the Jira API. Ensure it uses the correct Jira credential or is configured with the necessary authentication headers/body for your Jira instance.
  3. Configure GitHub Trigger:
    • In the "Github Trigger" node, select the "Repository" you want to monitor.
    • Copy the webhook URL provided by the node.
    • Go to your GitHub repository settings -> "Webhooks" -> "Add webhook".
    • Paste the n8n webhook URL, set the content type to application/json, and select "Just the push event" for triggers.
  4. Customize Code Node (Node ID: 834):
    • Review and adjust the JavaScript logic in the "Code" node to match your desired keywords for Jira issue keys and PR creation.
    • Modify the output structure to correctly pass data to subsequent Jira and GitHub nodes.
  5. Customize Jira Software Node (Node ID: 77):
    • Adjust the "Resource" and "Operation" to perform the desired action on Jira (e.g., Update Issue, Add Comment).
    • Map the data from the previous nodes (especially the Jira issue key) to the appropriate fields in the Jira node.
  6. Customize HTTP Request Node (Node ID: 19):
    • If this node is used for GitHub PR creation, configure the URL, method (e.g., POST), headers (e.g., Authorization: Bearer YOUR_GITHUB_TOKEN), and body to create a new pull request.
    • Map the necessary data (e.g., branch names, PR title, description) from previous nodes.
  7. Activate the Workflow: Once configured, activate the workflow.

Now, whenever a commit is pushed to your specified GitHub repository with the configured keywords, the workflow will automatically update Jira issues and/or create GitHub Pull Requests.

Related Templates

AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp

This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The “virtual executive team,” is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier 🎯 Core Features 🧑‍💼 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. 📊 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. 🕵️‍♀️ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. ⏰ 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline — key traits for early-stage success. 🗓️ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. 💬 WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. ⚙️ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. 🧩 Integrations Required Gemini API – for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API – for business and competitor analysis SerpAPI – for market research and opportunity scouting Google OAuth – to connect Sheets, Calendar, and Gmail WhatsApp Business API – for message triggers and responses 🚀 Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. 🧰 Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startup’s needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you 💡 Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business

ShadrackBy Shadrack
331

🎓 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

Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API

Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. It’s designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen

RapiwaBy Rapiwa
110