We are using Zapier for a bunch of automation. Sometime on Dec 2, 2024 we noticed a bunch of our Zaps failing. It ended up being because the Asana action (e.g., “Find a task”) was no longer returning an “ID” value. Previously the Asana actions were returning ID Field values the same as the GID value. Since we were relying on the ID value itself, a bunch of steps were failing.
This was due to a recent change in Asana’s API. Around this time, our Zapier Asana actions were showing as changed from AsanaCLIAPI@1.31.0 to AsanaCLIAPI@1.31.1
Since then, the errors we were getting were one of the following:
Required field “Task ID” (task_id) is missing.
Required field “Task” (task) is missing.
This required me to log into our Zapier account and:
Go into the Zaps that are experiencing this issue (almost a dozen)
Locate the Asana steps that are using the ‘ID’ field (numerous)
Replace these with the ‘GID’ field.
It took some time to figure out the issue, since the Zaps were still returning an “ID” Field in the Zapier interface… they were just showing as blank though.
Long story short, it’d be nice if there were some sort of actual changelog or roadmap for specific things like this. I realize the transition from ID to GID date back a while, but I don’t recall anything stating that ID itself would be stripped from use within Zapier (or from the API that it relies on). Simply overnight, a bunch of our Zaps failed without any heads up.
Sorry you experienced this. I’m not sure what AsanaCLIAPI is. I don’t think it’s something that we maintain. When I search for it, I come across this forum post and some pages on Zapier. One of them says that it is a “private app” in Zapier and:
This means the developers of these apps haven’t completed our full quality assurance steps. Zapier has limited details on these apps and as a result can’t offer support for them. If you have questions about these apps, please contact the person who gave you access to this Zap.
It sounds like a client library that someone put together for Asana within Zapier? As far as I know, Zapier maintains Zapier’s Asana integration. So we’re not able to know when it or something like the AsanaCLIAPI changes.
However, I can say:
When we make an API change, we look for integrations which might be impacted and contact the maintainers. We’ve done this several times with Zapier.
Zapier has always been responsive and works with us to prepare for the change.
The Asana API generally refers to object identifiers as gid and any change to those names (without notice) would probably indicate a problem that we would swiftly correct / roll back.
Sorry I’m not more helpful. It might be something to ask Zapier about.
Hmm. The Zapier team previously mentioned the following, which is why I had created this post, based on their initial responses:
The data returned in the Asana steps is directly from Asana’s API … This means that Zapier itself hasn’t made any changes to those IDs—we’re simply reflecting what Asana’s API provides.
Unfortunately, we’re unable to revert the app version on your account as the data is returned directly from Asana’s API.
Given the circumstances, I recommend reaching out to Asana’s support team for more information on why they are now returning the ‘GID’ instead of the ‘ID’ for a task.
You can see in the documentation here that we use gid for tasks . We have not used id, so if it is just passing along the response I don’t know how id would have ever been there.
If we ever made a change like that without notice, the API would be broken for most people. So I think there is a misunderstanding somewhere.
But note, based on that thread, I don’t see anything saying that the id output will actually cease to exist — especially not that it would have worked up until Monday with Zapier.
and some pages on Zapier. One of them says that it is a “private app” in Zapier and:
