Has message capability been built into the API?
Hi @James_Carl,
No, it has not yet been added to the API yet.
Hey, wondering if there are any updates to allowing access to Messages via API.
I’d be fine with an unsupported workaround, and also fine with read-only.
I’m trying to use LLMs to analyze my team’s task activities, so sadly this is critical, and I’ll be moving off Asana if there’s no solution.
Welcome, @Brett16,
Sorry, there’s been no update and no workaround, other than your using tasks like messages which many of us do all the time, instead of the Messages feature in the UI itself.
I’ve merged your post into another existing thread to consolidate.
Thanks,
Larry
Messages is a core part of the platform and we need to be able to post messages from our other systems to Asana. Without this, the value of the product goes down significantly. When will this be released?
Your sarcastic tone is not helping, please consider rewriting your message, with respect for the people like us trying to help.
Thanks
Ok done, sorry if it sounded like that.
Thanks for re-writing
I will happily give my point of view now!
In another thread you commented the former API lead said they had this on the roadmap, and sadly we don’t have access to the roadmap state. What I can tell is that after working with almost 300 clients, almost no one is using Messages, which could explain that the API team did not prioritise this part. It does not make it acceptable though, just wanted to point it out as a possible cause ![]()
Thank you, that’s helpful to know. We have created a kind of clunky workaround that we post tasks, but in every project we have a section called “Inbox” which is for “Tasks that are actually messages”. Not good but works.
Negatives are that we can’t search for only messages, and there’s no “Create follow up task” button. Plus it gets confusing and there’s risk that people actually start using “Tasks that represent messages” as actual Tasks, in which case it breaks the way we need to work in Asana. (We’re supposed to create “Follow Up tasks” rather than using “Messages” as tasks.)
I do what you describe all the time! We usually use a special emoji (like
) in front of the task name. You can also multi-home them all into a single project to be able to search for “discussion tasks” easily ![]()
Hello,
My team uses Messages as a method of status updates on major project milestones in addition to the completion of tasks. This may be somewhat redundant but with the large scale of projects we run, it provides a clear snapshot of where the project is to someone on the executive team.
With this we also want to have a Messages topic titled “Client Communication” with the latest emails added as a reply through Zapier (email as an attachment, not the text itself). I know I can send an email to the correlating project email that will add a new message, but this can get lengthy fast as it is the text itself.
This may only be one way to skin a cat as far as supplying latest client communications done through email efficiently for the executive level. Possibly there is a better method I’m not thinking of? Open to any ideas or other methods anyone else is using for this same purpose.
Thanks in advance.
Joey
Hi @Joey_Flynn and welcome to the forum!
There’s currently no API for Messages, so you’ll have to utilize a non-programmatic solution. You might want to post that question in the English Forum > Tips and Tricks section to get some more expansive eyes and input on it.
Thanks for the quick response, Phil. I will make a post there.
Hi, we’re building a script to migrate our data from clickup to asana. when creating projects - ideally I’d like to add messages to a project under the messages tab. Is that available via API? Are they too called stories, or are stories exclusively the “comments” under each task?
regards
- Björn
@Bjorn-S - I’ve moved your post to the thread for this topic. The short answer is no, messages don’t have any endpoints currently. That said, perhaps you can use a workaround from the thread. Alternatively, status updates behave a little bit like messages, except you have to set a project status with them which might be disruptive for you. You can check out the documentation and decide for yourself.
Ok thanks. we’re still not using Asana but will within a month, and I’m just trying to get my head around where we will communicate around a project and wanted to migrate our previous chat history. reading up here, It sounds like meta-data on the Project level is somewhat limited so we might be better off creating and “admin”-task for each project where things like attachments, messaged/comments and perhaps estimates can live? Seems convoluted, but is that what people are doing?
Thanks, I’ve looked into migrating our chat history as status updates but the API won’t let me specify date nor author so won’t work well for migrating our existing chats. Could work going forwards however.