Support True @Mentions in Chat Message API (Tagged Users + Notifications)
planned
Dawid Kotrys
The Chat Message API does not currently support true @mentions that populate the tagged_users array or trigger notifications.
Markdown like @Name is visual-only and doesn’t register as a real mention.
Requesting support for:
• tagged_users metadata population
• Notification triggering
• UI-consistent display (highlight + profile link)
Log In
Brendan W
Merged in a post:
Support native @mentions in Chat Messages API
Alexandre Guimenti
When sending chat messages via the API (POST
/v3/workspaces/{id}/chat/channels/{id}/messages), there is no way to
create native @mentions that trigger user notifications.
The @Name markdown format works correctly when
messages are sent from the ClickUp web UI, but when the same format is
sent via the API, it renders as a regular profile link (blue underline)
instead of a native mention tag (green highlight with notification).
We tested all available body parameters (content, tagged_users,
followers, assignee) and none of them produce native mentions.
Use case: We have an automated daily digest bot that posts team status
updates to product channels. We need to tag specific team members for
action items, but currently the bot cannot notify them.
Expected behavior: Either the @Name format should
work the same way via API as it does via the web UI, or a new body
parameter (e.g. mentioned_users) should be added to register mentions
when creating a message.
Ahmed Khalil
This is much needed feature but I am curious why Zapier integration can do this but the ClickUp API can't. Isn't Zapier using the ClickUp API as well?
Brendan W
Ahmed Khalil: Its using an internal API in that case, and to be honest it needs improvement as well! We'll improve it alongside adding true @mention support to our public API 🙂
Brendan W
marked this post as
planned
Maximilian Kimmel
We are having dozens of use cases, where we need this! Would e.g. be the killer argument to get rid of Slack.
Jason Joseph
Maximilian Kimmel many teams will still stick with Slack because the ability to generate a transcript from a shared audio/video clip is a core, free feature of Slack's Clips, not restricted to higher tiers. (On ClickUp if you aren't paying for A.I. access your voice clips are neutered.
Maximilian Kimmel
Jason Joseph This can well be. I was mostly referring to our own use cases. As we do build ML- and AI imnplementations since nearly 10 years already, we have an internal AI running, which is also a Clickup user (currently also still Slack, but with their restrictions, we are planning to move away from it soon). Therefore any AI-related things are easily doable for us - only thing, that is still unhandy, is that the AI cannot mention someone directly (comment endpoint works, but that is a rather ugly workaround).
Jason Joseph
Maximilian Kimmel cheers to your own AI.
Jeff Richmond
We need this and the ability to include emoji in the message markdown.