Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Hello there,

For my project, I have 2 Asana plans (A & 😎 and 5 GitHub repositories (1 to 5).

I want that, 

  • Whenever a task is created from one of the Asana plans (with a custom field indicating the destination repository), an issue is created in the right GitHub repository (with the Asana plan as a label), adding the Asana task link to the body.
  • When an issue is created in GitHub in one of the repos, the source Asana task is found in their plan, adding the GitHub issue link as a story (=comment)

I have managed to do this flow, which is working OK. But I have one issue that I don’t know how to solve.

For the first zap I am using “New Asana task” which triggers far too soon! A lot of times, I did not have the time to enter the custom field that indicates the repo, leading to failure. (cf screenshot)

Is there any other, better way to do this? Looking at “Updated Asana task” does not seem to be a right move. But maybe looking at “Tag Added to Task” in Asana instead of checking custom field on new task is a way to go?

 

Cheers,✌️


 

Hi @Louis MSF,

 

You can use a filter right after the trigger that will filter out everything that has the repository field empty. So that’s simply

 IF RepositoryField = EMPTY , HALT
 IF RepositoryField = NOT EMPTY , GO AHEAD

 Otherwise that tag system should work fine with a cost of adding tags every time you want to run it.

Hello @robschmidt thanks for your answer.

I finally managed to solve this using tags, it seemed to be the easiest way to do it

Cheers

Terms & Conditions