Hi @jadubenÂ
Good question.
That is correct the Zap step app account cannot be dynamically selected.
Believe you mean Task Comments, rather than Task Notes/Description.
Â
From the Asana API: https://developers.asana.com/docs/create-a-story-on-a-task
Adds a story to a task.
This endpoint currently only allows for comment stories to be created.
The comment will be authored by the currently authenticated user, and timestamped when the server receives the request.
Â
Depending on how many Asana Users you have, you may want to consider using Zaps w/ Filter conditions per User where the Asana Steps have the desired User account connected.
You’d have to authenticate each User account in Zapier here: https://zapier.com/app/connections
Yes that is what I was referring to. Does that mean I would need to have a separate Zap for every user in Asana? That seems really inefficient...
@jadubenÂ
Yes, else you’ll have to manage API Keys and authentication for each user with a much more advanced approach using APIs and Code.
How would I accomplish this? It seems less than feasible to set up a separate webhook for every user in our application, and the conditional run is limited to 5 branches.
@jaduben
I’m not a fan of using Paths due to the current limitations.
You can chain Zaps together using Webhooks. (e.g. 1:Many)
You’d need 1 Zap per Asana User involved that has their Asana account authenticated in Zapier here: https://zapier.com/app/connections
Â
Concept is
Zap 1
- Trigger: Asana
- Action: POST Webhook
- Check this help article about how to trigger multiple webhooks in 1 request:
-
Â
Zap 1.X
- Trigger: Webhook - Catch Hook
- Action: Asana
- Asana app account for User X
Â
Repeat for each Asana User