How to Sync GitHub Milestones to Jira Sprints with N8n

Workflows > New > Triggers > GitHub

Create New Workflow

Start a new N8n workflow and add the GitHub trigger. This will monitor for changes to your repositories and fire when issues are added to milestones.

1. 1Click 'New Workflow' from the N8n dashboard
2. 2Drag the GitHub node from the trigger panel onto the canvas
3. 3Select 'Repository' from the Events dropdown
4. 4Choose 'Issues' as the specific event to monitor

GitHub Node > Credentials > New

Connect GitHub Account

Authenticate with GitHub using a personal access token. The token needs repo and issues permissions to read milestone data and issue assignments.

1. 1Click 'Create New Credential' in the GitHub node
2. 2Select 'GitHub OAuth2 API' from the credential type dropdown
3. 3Generate a token at github.com/settings/tokens with 'repo' scope checked
4. 4Paste the token into the 'Access Token' field and click 'Connect'

Nodes > Logic > IF

Filter for Milestone Events

Add an IF node to filter only events where issues are assigned to milestones. This prevents the workflow from firing on every issue change.

1. 1Add an IF node after the GitHub trigger
2. 2Set the condition to 'action' equals 'assigned'
3. 3Add a second condition with 'milestone' is not 'null'
4. 4Connect both conditions with AND logic

Nodes > Data > Set

Extract Milestone Data

Use a Set node to pull milestone title, due date, and description from the GitHub payload. These fields will map to Jira sprint properties.

1. 1Add a Set node after the IF node's 'true' branch
2. 2Add field 'milestone_title' with value '{{$node["GitHub Trigger"].json["issue"]["milestone"]["title"]}}'
3. 3Add field 'milestone_due' with value '{{$node["GitHub Trigger"].json["issue"]["milestone"]["due_on"]}}'
4. 4Add field 'issue_title' and 'issue_body' from the GitHub issue data

Nodes > Apps > Jira

Search Existing Jira Sprints

Add a Jira node to check if a sprint already exists for this milestone. This prevents creating duplicate sprints when multiple issues are added.

1. 1Drag a Jira node onto the canvas after the Set node
2. 2Choose 'Search' as the operation
3. 3Set Resource to 'Sprint'
4. 4Use JQL query: 'sprint.name ~ "{{$node["Set"].json["milestone_title"]}}'

Jira Node > Credentials > New

Connect Jira Credentials

Set up Jira authentication using your instance URL and API token. N8n supports both cloud and server instances with different auth methods.

1. 1Click 'Create New Credential' in the Jira node
2. 2Select 'Jira Software Cloud API' for cloud instances
3. 3Enter your Jira domain (yourcompany.atlassian.net)
4. 4Generate an API token from id.atlassian.com and paste it with your email

Nodes > Logic > IF

Add Sprint Creation Logic

Use another IF node to create a new Jira sprint only if the search returned no results. This handles the create-or-link logic cleanly.

1. 1Add an IF node after the Jira search
2. 2Set condition to check if search results array length equals 0
3. 3Expression: '{{$node["Jira"].json.length === 0}}'
4. 4Label the true branch 'Create Sprint' and false branch 'Use Existing'

Create Sprint Branch > Jira > Create

Create New Jira Sprint

On the 'true' branch, add a Jira node to create a sprint using the milestone data. Map the milestone due date to the sprint end date.

1. 1Add a Jira node to the 'Create Sprint' branch
2. 2Set Operation to 'Create' and Resource to 'Sprint'
3. 3Map Sprint Name to '{{$node["Set"].json["milestone_title"]}}'
4. 4Set End Date to '{{$node["Set"].json["milestone_due"]}}' if not null

Both Branches > Set > Merge

Get Sprint ID

Add Set nodes on both branches to normalize the sprint ID value. The create branch gets it from the new sprint, the existing branch from search results.

1. 1Add Set node after 'Create Sprint' with field 'sprint_id' = '{{$node["Jira"].json["id"]}}'
2. 2Add Set node after 'Use Existing' with field 'sprint_id' = '{{$node["Jira"].json[0]["id"]}}'
3. 3Add a Merge node to combine both branches
4. 4Connect both Set nodes to the Merge node

Merge > Jira > Create Issue

Create Jira Issue

Add a final Jira node to create the issue in the identified sprint. Map GitHub issue data to Jira fields and assign it to the sprint.

1. 1Add a Jira node after the Merge
2. 2Set Operation to 'Create' and Resource to 'Issue'
3. 3Map Summary to GitHub issue title
4. 4Set Sprint field to '{{$node["Merge"].json["sprint_id"]}}'
5. 5Map Description to GitHub issue body

Workflow > Activate > Executions

Test the Workflow

Activate the workflow and test with a real GitHub issue assignment. Check both the create-new-sprint and use-existing-sprint paths.

1. 1Click 'Activate' toggle in the top right
2. 2Go to GitHub and assign an issue to a milestone
3. 3Return to N8n and check the execution log
4. 4Verify the Jira issue was created in the correct sprint

Drop this into an n8n Code node.

// Clean milestone title for Jira sprint naming
const milestoneTitle = items[0].json.milestone_title;
const cleanTitle = milestoneTitle.replace(/[^a-zA-Z0-9\s-]/g, '').trim();

// Clean milestone title for Jira sprint naming
const milestoneTitle = items[0].json.milestone_title;
const cleanTitle = milestoneTitle.replace(/[^a-zA-Z0-9\s-]/g, '').trim();
const sprintName = `Sprint: ${cleanTitle}`;
return [{json: {sprint_name: sprintName}}];