Integrate Github with Asana to track issues in repositories
Tags: github, asana, integrations, frontend
Published: 2021-12-16 12:41:41

Over time the need for different services grows in a SaaS startup, from something as simple as sending out a slack notification to something more complex as **Integrate Github with Asana**. 

In this case, maintaining and scaling these numerous Micro-services and Integrations is a huge developer overhead task.

Our previous guide covered sending a notification to Slack, and today we will move on to a bit more complex integrations ie; how you can integrate Github with Asana to track issues in repositories

## Let's get started! 🚀

**Step 1: Create a Asana account** 

We'll be setting up an automated pipeline to create tasks on your Asana project whenever a new issue is created on your Github repository. So make sure you have your you have an asana account, or you can create from [here](https://asana.com/create-account). 

**Step 2: Let’s begin with the integrations! 👩‍🔧**

All you have to do is, go to this [sample project](https://app.canonic.dev/projects/61ba6a6ab6586d0026b0f9cd?utm_source=dev.to&utm_medium=organic_article&utm_campaign=30daysofcanonic_uc_3&utm_term=step2_sample_project&utm_content=day_17) and click on the top right corner to clone it.

This project already has **Github<>Asana integration set up**. So after cloning the project, we are set to move forward and get started. 

![Project Clone](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/t9ysyn60k7lx8u0nhhmo.png)
 

**Step 3: Explore the API tab 👩‍💻**

In the same project, from the left-hand navigation bar, move to the API tab. 

There on the left-hand panel, you’ll find different divisions like - **Endpoints, Scheduled triggers, DB triggers, Integration triggers, etc**. In the integrations triggers, you should find an integration setup!

![Step 3](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/5ucrkfqb55glxkmiw7vb.png)
 

**Step 4: Setup GitHub Integration ✨**

Let's see how you can modify this Github integration trigger that runs whenever the count of issues in the repository changes, i.e. Whenever a new issue is added to the repository.

Click on the [**GithubIssues**](https://app.canonic.dev/projects/61ba6a6ab6586d0026b0f9cd/api-2?utm_source=dev.to&utm_medium=organic_article&utm_campaign=30daysofcanonic_uc_3&utm_term=step4_githubIssues&utm_content=day_17) trigger node and it’ll open up the Properties panel for it. 

![Github Integration](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/fy99di4cxfekp5tnfvxb.png)

You can see that we've selected the `ListRepositoryIssues` API from Github here. It'll **listen to any changes** to the response of this API and will **trigger your workflow** if the changes match any of the filters you've added. For this example, we are checking the list of the issues returned from Github is changing or not.

Now **add your own repositories details** in the API Configuration Section:

![API Configuration](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/zg0hxd0ay0ooyqb8var5.png)

**Step 5: Setup Asana Integration ✨**

Click on the `Asana` node and you can see the `Create a Task` API of Asana is already setup. **Add API Key** in the authentication section to connect with your account. 

![Asana Integration](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/zablepxi5ion2jtxk7on.png)
 
Move on to the `Optional` tab of the panel and add:

- `{{0.title}}` in the `name` field
- `{{0. body}}` in the `notes` field

![Optional](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vxj5bx9am8dkjzfq1939.png)

Once you've reached here, you've successfully Integrated Github with Asana to track issues in repositories. 🥳

Now every time an issue is created on your repository, you'll have it on your Asana Project too!

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/i5j3c0w677cgi7o40zod.png)

**Check out the sample project [here](https://app.canonic.dev/projects/61ba6a6ab6586d0026b0f9cd/api-2?utm_source=dev.to&utm_medium=organic_article&utm_campaign=30daysofcanonic_uc_3&utm_term=step5_here&utm_content=day_17)**
 

## Conclusion

Hope this guide helped you guys to track issues in repositories in an optimized and faster way. You can also **check out our other guides** [here](https://dev.to/canonic/).

Join us on [discord](https://discord.gg/9dyytsM) to discuss or share with our community. Write to us for any support requests at [support@canonic.dev](https://support@canonic.dev/). Check out our [website](https://www.canonic.dev/30-days-of-canonic/?utm_source=dev.to&utm_medium=organic_article&utm_campaign=30daysofcanonic_uc_3&utm_term=conclusion_website&utm_content=day_17) to know more about Canonic.