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.

Question

Unable to create Asana action because Zapier is not able to fetch the Teams list

  • February 6, 2024
  • 2 replies
  • 21 views
N

Unable to create Asana action because Zapier is not able to fetch the Teams list. 

1 Attachments
This post has been closed for comments. Please create a new post if you need help or have a question about this topic.

2 replies

communitymember
Forum|alt.badge.img+2

@nancyjain did you tried with other workspace 

Mehandi
ken.a
Forum|alt.badge.img+6
  • ken.aZapier Staff
  • Zapier Staff
  • February 7, 2024

Hi there @nancyjain,

Welcome to the Community! 🎉

I’m jumping in to see if I can help!

The error you’re seeing looks like a pagination issue this is a common error when there are too many data that the “Team” dropdown field can handle.

With that being said, would you be able to try adding the ID of the Team you're hoping to use in the Zap as a custom value? This can be done by selecting the “Team” field, clicking the “Custom” heading, and entering the project ID in the free text field. 

Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!

Terms & ConditionsAccessibility statement