Featured image with Logos for monday.com and GitHub, representing Unito's guide to syncing GitHub Issues to monday.com tasks with a 2-way integration.

How to Sync monday.com Tasks to GitHub Issues Automatically with 2-Way Updates

Published in Use cases on , last updated .

This guide will show you how to sync monday.com and GitHub with Unito’s automated 2-way integration for issues and tasks. This workflow can help you streamline software development projects; expedite ticket escalation; or align comments, assignees, custom fields, and more.

Our walkthrough will demonstrate a sync between monday.com tasks and GitHub issues specifically, but you can apply these same steps to sync other work items between either monday.com or GitHub and any other tool in your stack.

Why sync GitHub and monday.com with Unito?

Integrating GitHub and monday.com can help teams that aren’t familiar with GitHub collaborate more effectively with a development team.

It can save loads of time for engineers or project managers by eliminating the need to switch back and forth between GitHub and monday.com. You could triage development requests, project status, code bugs, feature requests and more.

This guide will highlight a specific monday.com GitHub integration use case with two primary goals:

  • Enable a team in monday.com (product, marketing, customer support, etc.) to create tasks in monday.com that automatically become bug report issues in GitHub based on specific criteria in Unito.
  • Set up a two-way sync between those selected issues and monday.com tasks so that as our dev team works on the assigned issues, the team in monday.com can see live updates.

Here’s a screenshot from our fully synced monday.com board and GitHub repository:

GitHub repo synced to monday.com board with Unito
In this demo, we’ll assign bug reports, but the same steps could be applied for assigning feature requests or other GitHub issues you might assign on a regular basis.

Before you connect GitHub and monday.com to Unito:

  • Ensure you have an account with the right permissions in both tools.
  • Add Unito to GitHub through the GitHub Marketplace if you haven’t already. This article can show you how.
  • Add Unito to your monday.com workspace here. You can also follow the steps below:

Add Unito to your monday.com workspace

  1. Login to your monday.com account
  2. Then, select Board Power-Ups > Apps Marketplace
  3. Type Unito in the search field
  4. Click on the Unito app, then Add to your account
  5. Now, hit Install, verify your workspace and board and Add Feature
  6. Authorize monday.com then Authorize again (the first button authorizes monday.com in Unito, while the second authorizes Unito in monday.com)
  7. Click Got it.

Step 1. Connect GitHub and monday.com to Unito

  1. Continue from monday.com or navigate to the Unito App and select +Create Flow.
  2. Select Start Here to connect your monday.com board and GitHub.
  3. Select +Add a tool to this flow in either column, then +Choose account to specify the GitHub repo and monday.com board you plan on syncing. The order in which you connect your tools doesn’t matter.
  4. Click Confirm.
Connect GitHub and monday.com to Unito
Note: The accounts you connect must have access to the board and repository you want to integrate.

Step 2. Tell Unito to create new tasks or issues in monday.com or GitHub automatically

Flow direction determines which of your tools will create new tasks or issues in the other. If you’re following our demo’s use case, select the arrow that points from monday.com to GitHub.

Pick a flow direction between monday.com and GitHub

If we had chosen a two-way sync, new GitHub issues would create tasks in monday.com, in addition to new tasks creating issues. As you’ll see in Step 4, we’ll later use a two-way flow for individual fields in our tasks and issues so that information between.

Select Confirm when you’ve chosen a flow direction. 

Step 3: Set conditions for how work items sync between monday.com and GitHub

This is where we can set up triggers to determine what actions taken in monday.com will cause new issues to appear in GitHub, or vice versa if you selected a two-way flow direction in the previous step.

Select Add a new trigger to begin setting your rules. There can be some variability here depending on your particular setup in each tool.

Set conditions for how work items sync between monday.com and GitHub

In the above example, we’ve told Unito to create GitHub issues based on monday.com tasks added to specific groups. In this case we can choose any or all of the groups above: Bugs Overview, Feature Requests, and Deletion Requests.

Below, you’ll see we’ve then told Unito to set a default label “bug” to any issue coming in from our Bugs Overview group in monday.com:

Find out more about setting rules.

Step 4. Pick fields to sync between GitHub and monday.com

Fields represent the details of your GitHub issues and monday.com tasks. Text, single-select, priority, assignees, and emails are all examples of fields you can map with Unito.

First, you’ll be asked whether you want to set up field mappings from scratch or let Unito do this automatically. If you select the auto-map option, you can still change your mappings afterwards. If you prefer a DIY approach, you should start from scratch.

What are Field Mappings?

Your fields will be automatically mapped for two-way updates. That means any changes in one project will be applied to the other. You can adjust any or all fields to sync one-way in either direction if you prefer. That would mean only the source field will change information in the destination field.

Select + Add mapping, then Select a field in both GitHub and monday.com to pair two fields together.

This is our basic set of field mappings synced between tasks and issues for the purposes of this demonstration:

GitHub monday.com 2-way Integration Field Mappings
In our demo, we’ve set up a repo for bug reports exclusively, so you could imagine feature requests being synced to another repo with a duplicate flow.

You can select the gear icon to modify the values of applicable fields. Above, we’ve told Unito that a GitHub issue should only be considered closed once the status changes to “deployed”. That way, our dev team will keep an eye on it until that point.

Learn more about field mappings and customization options for GitHub.

Click Confirm when you’re satisfied with your field mappings to proceed.

Step 5. Save, close and launch your monday.com GitHub integration!

And that’s it! You’ve just completed a flow between monday.com and GitHub. Congratulations!

If you’ve followed the steps above, your flow will now: 

  • Create an issue in GitHub based on monday.com tasks labeled “Bug Reports” from our specified group and board.
  • Enable technical and non-technical teams to collaborate between monday.com and GitHub with a view on ticket progress.

Here’s a closer look at a synced task and issue from our demo:

What’s next after a 2-way monday.com-GitHub integration?

If you’re interested in seeing what else you can do with Unito, here are some articles to help you power up your workflows:

Browse more resources for monday.com GitHub integrations