Add the ability to retrieve an Asana task’s comments/stories feed (all pages) to the Amazon Asana connector. Today the connector can read task fields but not the comment thread — and for change-management workflows, the comment thread is where the real decisions live.
Top 3 reasons this is critical
-
Comments are the authoritative source of truth, not the task fields. In change-management tasks, the most recent decisions — final country scope, send dates, deployment changes, approval status — are captured in the comment thread, often after the structured fields were last updated. A tool that reads fields but not comments retrieves a stale, incomplete picture of the task.
-
Every run today requires a manual human workaround. Because the connector returns no comments, the user must open the task, copy the entire comment thread by hand, and paste it back in — on every single task, every time. This defeats the automation and reintroduces exactly the manual effort the tooling was meant to remove.
-
The impact scales across teams, not just one workflow. Any Quick Suite agent or flow built on Asana change-management data inherits this gap. As more teams adopt Asana-driven automation, the same manual paste-in tax is paid repeatedly across every one of them.
What’s happening today (facts)
-
The Amazon Asana connector exposes:
SearchTasks,ListTask,CreateTask,UpdateTask. -
None of these return a task’s comments/stories feed. Task name, description, and custom fields come through; the comment thread does not.
-
Observed behaviour in live use (DSP Comms drafting agent, multiple tasks): the connector consistently could not pull the stories feed, and the workflow only completed because the user manually pasted the full comment thread.
-
Asana’s own API exposes comments via the Stories endpoint (
GET /tasks/{task_gid}/stories), so the data is available at the source — it is a connector coverage gap, not an Asana limitation.
Why this matters for productivity (assessment)
-
Assumption (high confidence): the manual copy-paste step adds several minutes of avoidable effort per task and is error-prone — a user can miss a comment, paste an outdated thread, or omit the newest decision, which directly undermines the accuracy of any downstream output.
-
Assumption (high confidence): the gap forces a “human-in-the-loop for data entry” pattern even when the rest of the workflow is fully automated, capping the achievable productivity gain of every Asana-based agent.
-
Fact: for our DSP Comms use case, comment content can override task fields (scope, dates, approvals). Without automatic retrieval, correctness depends entirely on the user remembering to paste — a single point of failure in an otherwise deterministic workflow.
What we’re requesting (specifics)
-
A connector capability to fetch a task’s full comment/stories feed by task GID, paginated to completion (not just the first page).
-
Return, per comment: author, timestamp, and text — enough to apply recency and attribution logic downstream.
-
Ideally, expose it as a first-class read operation (e.g.
GetTaskStories(task_gid)) alongside the existing task-field reads.
Bonus gap worth noting (related)
While the primary ask is comments, we also found the connector has no get-task-by-GID read at all — locating a single task requires paginating the whole project and matching the GID. A direct GetTask(task_gid) read would meaningfully improve reliability and speed for every Asana workflow, and would pair naturally with the comment-retrieval request.