Sarah Hum
complete
Canny for Asana has been approved! Head over to your Asana settings to set it up. Check out our help article to learn more.
A
Apricot Leopard
Sarah Hum: awesome, thanks to you, the folks who got the partnership, and the peeps who built & tested this integration. Just enabled the integration, and today is like day 1 for us again 💕
W
White Baboon
great
A
Amethyst Cockroach
Would love to know more about this!!
Sarah Hum
in progress
Asana Canny integration coming soon! Should be available in the next couple weeks.
A
Alternative Skink
Sarah Hum: any update on timing?
Sarah Hum
Hi Alternative Skink, we're just working with the Asana team now to get the integration approved. We'll update this post when it's available!
Sarah Hum
planned
R
Romantic Kangaroo
Sarah Hum: I would love to learn more about potential timing here!
P
Peach Rattlesnake
YES PLEASE!
V
Violet Hoverfly
Peach Rattlesnake: 🐵
I
Indigo Puma
Please!
A
Apricot Leopard
Sarah Hum Clickup integration went ahead of Asana. Can understand that a potential partner using your product earns "hey that's my baby" affection.
But to get real for a moment:
I brought Canny into my team and it has built traction in our company with dozens of internal users. We now have quite a few items requested by sales teams, CS teams, Dispatch (food delivery driver) teams, etc.
Without Asana integration our growing usage of Canny becomes more of a pain point than a source of value.
A
Apricot Leopard
And FWIW, prioritizing integrations is hard, for sure. If you look at my team's Canny boards, half the requests are for integrations. And those are only 20% of the requests for integrations we get overall from our b2b customers.
Sarah Hum
Apricot Leopard: Here are the reasons why we've prioritized ClickUp over Asana:
- More people are asking for a ClickUp<>Canny integration
- The ClickUp team is working with us on the integration, making it better and easier.
Glad to hear your team is enjoying Canny. Can you be more specific about where the pain is?
A
Apricot Leopard
Sarah Hum: The pain is from cycles of manual work between AMs and PMs, over the lifecycle of each post in our Canny workspace that gets prioritized into our working tools. One-time manual forward publishing from Canny -> Asana is already time consuming enough, manual work to back-propagate status changes in working tools is pain x (2-5). But forward publishing is required table stakes, and back-prop is necessary to trigger the sweet automatic notifications to voters that attracted me to Canny.
Without automation of forward && back status changes: Mo' velocity, mo' problems.
We have automated pipelines across the toolchains for most every planning and production artifact, specifically to minimize the need for updating status in anything more than one tool.
Asana was not been particularly easy to work with as a 3rd party developer. Just like Slack was back in 2014-2015, when 3rd party access was granted case by case, and the functions exposed were barely worth mentioning. But Slack got it together, and Asana's bad old dev platform days are mostly in the past.
Sarah Hum
Apricot Leopard: Thanks for elaborating here. This aligns with what we were thinking for this integration. Good to know Asana's platform should be friendly to work with. You'll know when our team prioritizes this integration!
A
Amethyst Beaver
Can we please please please integrate this
X
Xeric Koi
This would be unreal, would close the loop for our product team so nicely
Load More
→