“I need help setting up a Quick Flow to automatically create Asana tasks from my chat agent’s collected information”
Can you be a bit more specific about what you are asking for help?
Surely, Jacob
And thanks for replying!
I’ve created a chat agent (ISS Research Office Hours Intake Assistant) that should collect intake information conversationally and create tasks directly in my Asana project (ID: 1213611389981324) with automatic routing to regional sections. However, the agent is displaying the Asana form to users instead of creating tasks in the backend. This defeats the automation purpose — users should only interact with the chat and receive a confirmation message, while I (as the owner) manage the Asana tasks and calendar assignments. I’ve linked the Asana integration and updated the agent prompt to call Asana.CreateTask with section routing logic, but it’s still redirecting users to the form.
Additionally, I’m unclear on whether using a Quick Flow instead of a chat agent would be better for this use case. What are the benefits and possibilities of Quick Flows for Asana integration compared to chat agents? Would a Flow handle the Asana task creation more reliably without showing users the form?
Any guidance on fixing the agent’s Asana integration or recommendations on the best approach (agent vs. Flow) would be appreciated!
I would check this out: Connecting a Flow to Asana to pull project statuses .
In my opinion, my litmus test when creating a chat agent vs a Flow is the complexity of the task and the variability. If the input or guidance often requires you to ask follow up questions, or ask the end user to provide more information, the a chat agent is great at doing that. Otherwise Flows is an excellent choice. You can even use the chat agent within Flows to not only control your instructions, but prevent users from taking action without providing the required information using reasoning groups. e.g. Has user satisfied x, y, z. If not do not allow them to create the task. As for the chat agent, you can embed workflows into the task. e.g. When user asks “how do I use this chat agent”, you respond with usage section in your instructions. Or when user says “I want to create a task”, You do 1. <> 2. <> 3. <> and ask for for information if the following rules are not satisfied.
As for the form, this is a human approval to verify your work and is in place for a specific reason. If you schedule the Flow, there is an automated approval button for actions.