Community Central

If your Agent Studio plugin used to respond in 2 seconds and now takes 8, you might not have a bug, you might have an architecture problem.When you stack multiple actions back-to-back in a conversation process, the AI has to stop and process everything after each one. More actions, more data, more thinking, and your user is stuck watching a spinner.The fix: either add a natural user interaction between actions (like collecting a required field), or bundle your chained actions into a single compound action that runs behind the scenes.One reasoner turn. Cleaner context. Faster plugin.📬Want more tips like this? Subscribe to the Agent Studio Developer Newsletter in Community or via email.

We recently hosted a session on how to move from AI ambition to real enterprise automation — and what it actually takes to deploy AI agents that work across the business.Here are the key takeaways 👇 🔎 The Core ChallengeEnterprise work rarely lives in one system.Even simple tasks often span:• Multiple applications• Several approvals• Manual handoffs• Status chasing and follow-upsThe result? Operational friction, slower execution, and teams stuck in low-value work. 🤖 What Makes AI Agents Actually

Hey,Your plugin went from 2 seconds to 8 to respond to your user. You didn't change anything. You just added a second action to the conversation process, then a third, then a fourth. Now the user stares at a spinner and you're filing a bug about "slow plugin response times."It's not a platform bug. It's an architecture problem, and there's one golden rule that fixes it.The Golden RuleHere it is:Never execute two action activities in a row in a conversation process without collecting a slot in between.That's it. One sentence. The single most important architecture pattern in Agent Studio.Why it mattersHere's what actually happens when you chain actions in a conversation process. Conversation processes are deterministic code paths: the reasoner will execute each activity in order regardless. But between each action activity, the reasoner still has to process the output. Each

Huge thanks to everyone who joined Sarah Chudawala, Senior Customer Success Manager at Moveworks, and Joe Birney, Director of IT Product Enablement at Motorola Solutions, for an honest and insightful look at Motorola’s journey from a homegrown support bot to a scalable, enterprise-ready AI assistant: Echo, powered by Moveworks.Here’s your quick recap with key takeaways 👇 🧩 The “Build vs. Buy” MomentMany organizations have the talent to build internal to

We can find the available time of our colleagues using the findMeeting API and this will give us the available slots of the user. This works perfectly for my calendar.Usecase: For the executive assistant, to get meetings on behalf of a shared or delegate mailbox that they have access to, this API doesn’t work.During our implementation:The findMeeting API works correctly for the authenticated user:https://graph.microsoft.com/v1.0/me/findMeetingHowever, when attempting to retrieve available meeting times for a shared or delegate mailbox using:https://graph.microsoft.com/v1.0/users/{sharedMailboxEmailId}/findMeetingthe request returns an "Unsupported Scenario" error.Even

​Objective:  The objective of this design is to enable the consumption of Moveworks Large Language Model (LLM) capabilities from enterprise platforms such as ServiceNow, rather than restricting LLM usage solely to a conversational chatbot interface. This document uses ServiceNow as a reference integration platform to illustrate the approach.  Business Use Case Overview The proposed integration enables multiple high‑value business use cases designed to improve operational efficiency, service quality, and knowledge reuse across IT and business teams.The solution supports, but is not limited to, the following cases like: 1. Incident Summarization a

March roundup is packed with practical updates to help you move faster: March brings powerful platform updates, new ways to customize and test your Assistant experience, and exciting momentum across our agent ecosystem – including Initiative Designer now live in the Marketplace. Dive in to catch up on what’s launching, rolling out, and happening in the community this month👇📣 Coming Soon: Transition to Now Support starts on March 16Support is moving to ServiceNow’s Now Support: All new Moveworks support cases must be submitted through the Now Support Portal starting March 16, making it faster and easier to get the help you need and elevate your experience with Moveworks. What to expect during the transition: Open cases will be migrated to Now Support the week of March 16 (and remain accessible in the current portal during the transition). Closed cases will not be migrated but can be requested through Now S

If you're not sure where to start in the community, this is one of the most useful things you can do in the first few minutes.Each product forum has a Subscribe button in the top right corner. When you subscribe, you'll get an email notification any time a new topic is posted in that space. No need to remember to check back manually.How to do it:Navigate to the product forum that matches what you're working on (AI Assistant, Agent Studio, Enterprise Search, etc.) Look for the Subscribe button in the top right Click it. That's it.You can subscribe to as many forums as you'd like. If your focus changes or the emails get to be too much, you can unsubscribe the same way.Not sure which forums are relevant to you? Start with the ones that match your current Moveworks prod

Want to get smarter about managing analytics access in Moveworks? Our latest Academy course walks you through everything you need to know about data governance, roles, and Custom Views.You’ll learn how to: Structure analytics resources safely Apply the principle of least privilege Manage permissions with confidence Share insights across teams without exposing sensitive data Perfect for program owners, admins, and analysts, this course combines practical examples and best practices to help you make informed decisions about analytics access. Click here to take the course.

Hello,I am new to the community and getting my feet wet by starting withMoveworks Agent Studio Developer: Level 1 Certificationfor which I will need access to Agent Studio as per the instructions. Could you please guide me with the next steps to get access.Much appreciated. Thanks,Rekha

Hey builders!We just shipped a brand new docs experience. If you've been to help.moveworks.com recently, you already noticed — we moved everything to docs.moveworks.com.New platform, new URL, and a bunch of upgrades that make finding what you need way faster. Here's what changed and why you should care. Finding Your Way Around: Product SwitcherThe biggest navigation change: there's now a product switcher at the top of the docs.Instead of scrolling through one massive sidebar trying to find the right section, you pick your product area first — Agent Studio, APIs, platform guides — and the sidebar filters down to just what's relevant.If you've ever ope

Hey,I used to write slot descriptions like mini-prompts. "Extract the Jira ticket ID from the user's message. If they say 'my ticket,' look up their most recent open ticket." Paragraph-long instructions trying to get an LLM to do what a single API call could do.That's what resolver strategies replace.Last issue we unpacked the basics — inference policies, descriptions, validation. By the end of this one, you'll know how to wire up resolver strategies, when to use static vs dynamic resolvers, and how disambiguation keeps your plugin from guessing.One Big Thing: Resolver StrategiesSlots collect inputs. But "my bug ticket" isn't an ID. It's context. Something has to convert that into a structured value your action can use. That's what resolver strategies do.You can attach a resolver in two ways:On a custom data

We are new to Moveworks and very excited for what is coming for us. During demos and some testing, we noticed that that when a chat with a live agent is started, the end/close button’s position could potentially make it easier for users to unintentionally close the chat. I would love to hear comments from people from this community and see if it is only us 😅Thank you

In December, we united with ServiceNow to deliver one AI front door for employees across the enterprise to get work done.Now, we’re ready to show you what’s possible by integrating our consumer-grade AI and enterprise search with ServiceNow’s unified portal and autonomous workflows to turn employee requests into governed, end-to-end execution for over 200 million employees across the globe.Join us and ServiceNow Thursday, February 26 at 10 AM PT to learn more and experience the frontier of work firsthand. Learn more and sign up. 

Big thanks to everyone who joined Esther Dsouza and Will Davis for this technical walkthrough on how ServiceNow teams are deploying agentic AI with Moveworks in live production environments — with real examples of search, actions, approvals, and proactive workflows.Here’s your quick recap with key takeaways 👇 🧠 The Big Idea: ServiceNow + Moveworks = An “Intelligent Front Door” for EmployeesServiceNow is your system of record — Moveworks becomes the conversational layer that helps employees find answers and take action across systems without needing to know where

The ProblemMoveworks has a native ServiceNow approvals flow that includes three plugins (Approval Information, Update Approval Record, and List of Approvals). In a perfect scenario, the user would simply ask to show details on their approvals and ask to approve only one record at a time. The more common scenario, users ask to approve multiple records at once and because the chat bot supports planning it will attempt to complete this task and sometimes it can work, but most of the time it fails. The SolutionWe can disable the native plugins and create a custom plugin that supports bulk actions and recreates the native functionality. The downside to this approach is that the calls would be real time and I suspect the native plugins ingest the approval details which is why it serves the inf

The Agent BuilderYour plugin keeps asking users for things it should already know."What's your employee ID?" — it's in their profile. "Which ticket?" — they just mentioned it. "Who's the requester?" — obviously them.This is the slot inference problem. And once you understand how slots actually work, you stop building plugins that interrogate users and start building plugins that just... get it.By the end of this issue, you'll know how to configure inference, write tight descriptions, and validate inputs — so your plugin collects what it needs without wasting round trips.One Big Thing: Slots, UnpackedSlots are the inputs your plugin needs to do its job. "Close my Jira ticket" needs a ticket. "Book a meeting" needs attendees. "Submit PTO" needs dates.slots: ticket: type: u_JiraIssue de

February’s roundup is packed with practical updates to help you move faster: from new Agent Studio resources and product enhancements to live sessions focused on hands-on developer use cases. Read on to see what’s new and what’s coming this month 👇🤖 February Webinars and Office HoursFeb 4 — Live Product Tour Feb 5 — 📌 Developer Office Hours: Sign up now Feb 18 – 7 Ways Agentic AI Helps Employees Move Faster in ServiceNow🚀 Product UpdatesCheck out the late

Easy win for the Moveworks Web Assistant. We are a Google shop and maintain a required pinned folder of bookmarks for all employees, giving them quick access to the most important places to find information. We recently added the Web Assistant URL to this bookmark list and have found that it’s helping employees access the assistant more easily and driving adoption up. It’s been a simple, quick win for the team.See Screenshot below.

Join us tomorrow for a technical deep-dive into the Moveworks + ServiceNow integration.We'll cover:Connecting knowledge bases, forms, and ticketing through the platform Real-world agent configurations already running in production Setting up ambient agents with proactive, event-driven workflows Marketplace plugins that speed up your deploymentRegister here!Joining? Leave a comment below!

Hello Team,I have recently created a Confluence connector and successfully ingested internal Confluence pages into our Moveworks bot. Most of the articles/pages were ingested without issues.However, I noticed that a restricted page in Confluence (with page-level permissions limiting access to certain users/groups) was not ingested by the connector.Could you please clarify if this is the expected behavior of the connector? Does the connector skip pages that have restrictions, or is there a way to include them in the ingestion process? 

HeyI built two Agent Skills last week.The first one turns rough text into polished frontend code using React and Tailwind CSS — drop in some ideas or a sketch, get back a website in seconds. The second one reads all my writing samples and generates a style guide so that anything my assistant writes next sounds just like me.Both took about 20 minutes. Just markdown files with clear instructions.Here's what a snippet of the 150 line voice-analyzer skill looks like:# Voice Analyzer SkillWhen given writing samples:1. Extract sentence patterns (length, rhythm, punctuation)2. Identify vocabulary preferences (technical vs. casual)3. Note structural habits (how paragraphs open/close)4. Output a style guide with 3-5 concrete rulesUse this guide when writing future content.They're simple. Markdown Files. No Infrastructure. No Loops. No Orchestration. Chef's kiss.And t

Device issues are one of IT’s biggest headaches, but many can be proactively prevented. ​@mirel.ivan from Keysight built an Ambient AI agent that is able to listen to Nexthink events and alerts device owners the moment a problem arises. It then evaluates the event details, compares them against available Remote Actions, and automatically runs the right one to fix the issue. This agent can powerfully reduce manual triage and helps keep employees productive, rather than troubleshooting. Check out his video here i

We’re kicking off the year with fresh product updates, upcoming live sessions, and exciting momentum as we build toward what’s next. Dive in below to see what’s new and what’s coming this month 👇 🚀 Product UpdatesCheck out the latest highlights below - full details for this cycle posted our Product Updates hub:🗺️ Live Product Roadmap: [For Customers & Partners only] Our product roadmap is now live in the Moveworks Community, giving customers real-time visibility into what’s shipping next, with interactive roadmap items you can explore, upvote, and discuss as plans evolve. 🎉 Enterprise Search upgrades: Search now intelligently groups related documents