Skip to main content

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

Workflow preview

Workflow preview
100%
Automate GitHub PRs & JIRA updates from Git commit commands-single repo preview
Open on n8n.io

Important notice

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

1. Workflow Overview

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

Best for

  • DevOps automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.httprequest, n8n-nodes-base.githubtrigger, n8n-nodes-base.stopanderror, n8n-nodes-base.jira, n8n-nodes-base.stickynote

Source and attribution

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

Original n8n.io source

1.1 Workflow description

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

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

For Custom Worflow Automation

Click here- Get Started

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 - Commit Message Breakdown

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

Block 2 - Check for PR commands

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 3 - Request to create PR

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 4 - Github Trigger

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

Block 5 - Invalid commit message

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

Block 6 - JIRA Task does not exist

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

Block 7 - Check for task completed command

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 8 - Get task details for PR

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

Block 9 - Get Task Details without PR.

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

Block 10 - Check if task exist

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 11 - Update task status after PR

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

Block 12 - Check whether a PR already exists

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 13 - Update the task status without PR

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

Block 14 - Check if PR exists

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 15 - Check if task exists

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 16 - Sticky Note

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

Block 17 - Sticky Note1

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

Block 18 - Sticky Note2

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

Block 19 - Sticky Note3

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

Block 20 - Sticky Note4

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

Block 21 - Sticky Note9

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

3. Summary Table

Workflow Automate GitHub PRs & JIRA updates from Git commit commands-single repo
Complexity advanced
Nodes 21
Categories DevOps
Author Intuz
Published 01 Aug 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/6773/6773.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 Automate GitHub PRs & JIRA updates from Git commit commands-single repo do?

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

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 DevOps use case.