Briefly describe (1-2 sentences) the Bug you’re experiencing:
Steps to reproduce:
Create a project
Create 2 sections in the project and name them Sec A and Sec B. They should be ordered as Sec A, Sec B going from left to right in the Board view of the Asana project
View the project in Board view
Open Zapier and create a random Zap that does anything when " Updated Task in Project in Asana" happens
Create a test task in Sec A, and give it any name Test Task or something
Move the task from the first column to the left to the second or third column
You’ll notice that nothing happens. Asana doesn’t send update to Zapier even though the task has changed sections.
I’ve attached a screenshot of the resource_type’s name changing after force pulling data by Zapier from Asana for testing.
When left to do it on its own, Asana won’t acknowledge that as an update to the task, and send Zapier the data.
A hack I had to do to make it work, is to type anything in the notes section of the task, only then it recognizes the update to the task as something it needs to tell Zapier, and reports the change of section as well as the changes in the notes I made.
It also doesn’t recognize when people comment on the task as an update.
Does anyone have the same issue?
Can you guys resolve this bug?
Browser version:
Used multiple browsers, same problem.
Almost positive it’s a Zapier issue. Asana’s current architecture of Sections is relatively new and as I recall Zapier was never updated to know anything about Asana Sections.
I’d tend to agree with Phil. Perhaps you could use Asana’s Rules (if on Business) as your trigger, or another third-party connector, but I’m not sure specifically which one can handle this better.
@anon57557818, I’d recommend reaching out directly to Zapier Support team (contact@zapier.com). To avoid re-explaining everything, feel free to share the URL of this public thread!
Hey Phil, we’ve interacted before! I’m a veteran automation specialist and I can say that there are currently some inconsistencies in the outputs.
I too am getting the same results after hours of tinkering and am beginning to lose hope:
I have tested triggers within Zapier according to custom field updates and those work half of the time as sometimes the update is triggered but somehow the data provided by Asana is empty.
As a workaround, I tried updating a field but filtering according to the stage name but here inconsistencies are plaguing the workflow : half the time the Asana data gives the last stage the task was in, half the time it gives the current stage.
I have also found that section change and comments do not trigger the Updated task Zapier trigger.
What should have been a simple workflow setup and ready to go in less than an hour, has become a headbusting rabbit hole.
I can say with a high degree of confidence that the issues you’re describing are on the Zapier side, not Asana. The reason I say that is I know from personal experience with well over a thousand Flowsana users that Asana webhooks properly report changes to a task’s custom fields and section.
I would recommend reaching out to Zapier (they’re the authors of their Asana integration). They can always reach out to Asana engineers if they need assistance and I’m sure Asana will give them any support they need.
Alright, I’ll go further down the rabbit hole and try creating tags with Flowsana and triggering based off of that from Zapier.
If this doesn’t work, I’ll try setting up with webhooks instead.
Perhaps it is indeed on the Zapier side of things however (venting here) it is quite mind-numbing that Zapier integration issues and “advanced” stage change automations are mentioned in countless threads in the community since 2020 at least.
Sadly, I see lumps of people that are running into the same issues trying to set up some simple workflows and that only have your solutions to rely on to fix those problems…
