TL;DR: Agents got a lot better this month at knowing who to involve and when. They can now resolve role groups (author, assignees, approvers, followers) into live @mentions at runtime , read and act on people-type custom fields, and combine the two to @mention the actual people stored in a field . Three new prebuilt agents are ready to turn on, the Microsoft Teams integration adds group chat posting, and MCP v2 is live for everyone.
Hey Community! 👋
Welcome to Wrike Agent News!
This monthly digest features updates, learnings, and how-tos from the Wrike R&D team.
This month is about people! Agents can now figure out the right people to notify on each work item instead of pinging the same fixed list every run, and judge whether a change is even worth a notification before sending one. As well as that, we have a batch of new default agents, a Teams upgrade, agent pausing and the MCP v2 launch.
Here are the six major shifts landing this month:
💬 New Action: Agents Can @Mention Users Dynamically
Previously, picking a user in the @ picker meant pinging the exact same person every single run . Mentioning different project owners meant cloning the entire agent.
Now, you can reference role groups directly in your instructions, such as "notify the author" or "this task was completed by the assignees but approval is still expected from the approver." The agent resolves these roles at runtime based on whoever is actually assigned to that specific item. Every name lands as a clickable, live @mention that triggers a real notification .
👤 Agents Can Read and Act on People (User) Custom Fields
Agents can now read people-type custom fields, use those values in their reasoning, and assign work based on them (no more “Action failed” when a task’s assignee lives in a custom field instead of the instruction). “Assign this task to whoever’s in the Project Lead field” now works, for both single- and multi-user fields. This closes the gap for teams that store responsible or involved people in fields (populated by intake forms, say) rather than hardcoding them per agent.
🔗 Where It Comes Together: The 2 Features Above, Combined
On their own, the two updates above are useful. Together, they unlock the scenario customers have actually been asking for.
The first taught agents to turn a role into a live, clickable @mention at runtime . The second taught them to read the people sitting inside a people-type custom field. Put them side by side and an agent can read the users listed in a field and @mention those exact people in a comment (dynamic @mentions of users stored in custom fields ).
So an agent can pull the stakeholders from a people field (say, the reviewers on an intake form) and post a comment that notifies those specific users directly: a different set of people on every item, all managed by one agent.
Example prompt: You might give the agent something like:
Post a comment “Hi <users listed in “stakeholders to keep informed” custom field>! Task <task name> from <author> which is assigned to <assignees> is ready for your review!”
🤖 3 New Default Templates
We have rolled out three more prebuilt agents you can turn on without configuring from scratch:
- Revision tracker: On a status change, it updates a custom field and posts a comment.
- Project coordinator: On a new item, it assigns unassigned subtasks, sets missing due dates, and emails the CSM.
- Missed deadline agent: When a finish date passes, it posts to Slack and sends an email.
Good starting points on their own, and useful templates to clone and tweak.
🤝 Wrike AI agents in Microsoft Teams: Sending messages to chats
Agents can now post a notification straight to a Microsoft Teams group chat, not only to a channel. The agent composes a message from the work item’s context, following the instructions you give it in the action, and the Wrike Teams app delivers it (not the agent directly, and not under the name of whoever set up the action). Every message carries a link back to the originating Wrike item.
⏳ Agents That Can Pause
You can now tell an agent to wait before it acts.
An agent triggers on a new Wrike item tied to a Salesforce deal. The deal's data (amount, account, close date) arrives on its own clock: Unito copies it from Salesforce into Datahub, which takes anywhere from a few seconds to a couple of minutes. The agent doesn't wait for it. It reads those fields, finds them empty, and acts on the blanks. Write a wait into the agent's instruction, "wait two minutes before doing anything," and it holds off until the data has landed.
Limitation: this is a timer, not a handshake. The agent waits the time you asked for; it doesn't check whether Unito finished. If the sync runs long, the agent still goes early. Set the wait longer than the sync usually takes, and treat it as reducing the odds rather than eliminating them.
Pro tip: time it before you set it. Watch how long the external update normally takes to land, then add margin.
Conversational Builder Improvements
📁 UI chips in the conversational builder
Choose a location or user from a chip in the chat rather than typing its name and hoping the builder finds it. Especially helpful when appointing an agent to the right location!
💾 Fix: When you try to leave a chat, the builder now reminds you to save and appoint your agent
The conversational builder is meant to be the easy way into agents, but it didn't reliably tell you what to do once yours was ready, so it was easy to close the chat and lose everything. Now, if you try to leave with an agent that isn't appointed yet, a popup lets you Add agent (appoint it right away) or Save for later, so your work doesn't vanish.
🔌 MCP Server v2 is live
Don’t forget we shipped MCP v2: it’s now live, turning your conversations into coordinated work in Wrike. Read more here: Wrike MCP v2 is now live for everyone.
📡 On Our Radar
- Agent action: Create an item from a blueprint
- Agent action: Create a new item with a formatted description
- AI agents working with attachments research - let us know if you’re interested, or schedule a call to share your use cases!
Questions?
Want help setting up any of these? Reach out in the comments. Need a different agent type? Contact your customer success manager. Found a bug or have feedback? Use the in-product feedback link or let us know below.
Found this update helpful? Let us know with a quick reaction (Like👍, Agree 🙂, Insightful💡) or drop your thoughts in the comments below!
