Following on from Any way to create User @mentions using API? - the rich-text markup there works, and John_Vu’s note that the API does not auto-add the mentioned user as a collaborator, with addFollowersForTask as the follow-up, is clear and matches what I see. I add the follower, and the note does arrive. My question is about where it arrives.
A mention posted through POST /tasks/{task_gid}/stories with the documented markup never appears in the mentioned user’s Inbox when that Inbox is filtered to “Mentioned”. With the addFollowersForTask call it arrives in the unfiltered Inbox, but as activity on a followed task rather than as a mention. The identical comment typed in the web UI, by the same user on the same workspace, does reach the filtered view.
That makes the documented approach unusable for the case it is most needed for. Filtering the Inbox to “Mentioned” is the normal way to keep a busy Inbox readable, and an agent posting review notes through the API cannot reach a person who does that - the write succeeds, the comment is correct on the task, and nothing surfaces. There is no error and nothing logged.
Tested on 6 November across three markup variants (self-closing as documented, with inner text, and empty paired tags; all stored identically), with and without the follower pre-add, on new and pre-existing tasks, and with the web UI comparison performed signed in as the same user whose token the API calls use. Reading the story back confirms the mention resolved: the anchor comes back annotated data-asana-type="user", data-asana-accessible="true", with the right data-asana-gid and the user’s display name as the anchor text.
The new Notifications API does not distinguish the two cases either. Both an API-created mention and a UI-typed one return story_resource_subtype: comment_added, so a client cannot reproduce the “Mentioned” filter itself as a workaround.
Two questions. Is an API-created mention intended to be excluded from the “Mentioned” filter? And if it is, is there any supported way for an integration to reach a user who filters their Inbox that way?
Happy to send a full reproduction with GIDs and request/response bodies privately.