Skip to main content

Moveworks Beyond MS Teams and AI Assistance

  • February 7, 2026
  • 16 replies
  • 1132 views

rajeev.saraf
Forum|alt.badge.img+3

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 and Contextual Analysis

The integration enables automatic summarization of incidents by consolidating incident descriptions, activity logs, and resolution notes into clear, concise summaries.

 

2. Intelligent Solution Generation for Incidents

Based on historical incidents, known errors, and existing knowledge articles, the solution can recommend or generate potential resolutions for newly raised incidents.

 

3. Automated Knowledge Article Creation

Resolved incidents can be automatically transformed into structured knowledge articles, ensuring organizational learning is captured and reused.

 

4. Agile Development Support: Documentation and Test Artifacts

The integration supports Agile delivery by generating key artifacts such as:

  • Release notes
  • Acceptance criteria
  • Test cases
  • Functional documentation for user stories and requirements

 

Implementation Overview

 

The implementation involves integrating Moveworks with ServiceNow to deliver seamless, AI‑driven capabilities directly with ServiceNow platform. This integration enables the availability of ServiceNow‑native forms and modules that allow users to invoke Moveworks use cases designed and governed through the Agentic Studio platform.

The approach ensures that AI capabilities are embedded where users already operate, minimizing disruption while maximizing adoption and business value.

 

Key Highlights

 

Native ServiceNow Experience

Moveworks operates directly within the ServiceNow interface, allowing users to leverage intelligent automation without switching platforms or tools.

 

Platform Independence

The solution is to be independent of Microsoft Teams or Moveworks AI assistants, enabling flexible deployment across business units and reducing reliance on specific collaboration tools. This supports broader accessibility and long‑term scalability.

 

Reusable Use‑Case Design

Use cases originally designed for MS Teams or AI assistance can be reused and extended within the ServiceNow interface without redesign or redevelopment effort.

 

Prototype Overview

 

The prototype has been developed in alignment with the above design, leveraging Moveworks Large Language Model (LLM) skills and publishing the generated responses through ServiceNow‑native modules. The implementation demonstrates end‑to‑end interaction between the two platforms.

The prototype has been implemented using a ServiceNow Personal Developer Instance (PDI) and a Moveworks Sandbox environment.

 

Moveworks Platform Implementation

The following components were configured within the Moveworks environment to support request handling, orchestration, and secure communication:

  • Listener
  • Plugin
  • Compound action
  • HTTP Actions
  • Credentials

ServiceNow Platform Implementation

The following ServiceNow artifacts were created to enable invocation, authentication, and user interaction:

  • Outbound REST Message and Methods
  • Application Registries
  • OAuth Entity Profile
  • UI Action
  • Client script
  • Some custom fields

 

Disclaimer: 

  • The demonstration is only a working prototype, and it is not a fully equipped E2E solution
  • The goal of demonstration is to highlight Moveworks capabilities and possibilities

I shall be documenting required update set from PDI and Moveworks configuration soon...

 

Check out the video demonstrating same - 

 

https://youtu.be/yuBogootkYo

Regards,

Rajeev Saraf

LinkedIn - https://www.linkedin.com/in/rajeevsaraf9/

16 replies

Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • February 11, 2026

Hey ​@rajeev.saraf , great write-up and cool prototype! Love seeing the community push the boundaries of what's possible with the platform.


Wanted to flag two things that are directly relevant to what you're after:


1. Conversation API
We recently announced a Conversation API that will let you make headless requests to the Moveworks assistant programmatically, no Teams or chat UI required. This is essentially the "platform independence" layer you're building toward. You can call it from ServiceNow (or any platform) via REST and receive the same AI-powered responses. Might simplify your integration significantly since you wouldn't need to wire up individual plugins/compound actions on the Moveworks side — you would talk to the assistant directly.
 

2. Ambient Agents
For several of your use cases — incident summarization, solution recommendations, knowledge article generation — Ambient Agents can already handle this today. You can set up an ambient agent that triggers when a new ticket is created (or updated), analyzes it, and posts findings directly as a work note on the ticket. No Teams dependency, no user-initiated interaction required, it all happens automatically in the background. This covers a big chunk of your use cases out of the box.


Between the two, you might find you don't need the custom ServiceNow-to-Moveworks REST plumbing at all.

Would love to hear how these fit into what you're building!


rajeev.saraf
Forum|alt.badge.img+3
  • Author
  • Known Participant
  • February 11, 2026

Hey ​@rajeev.saraf , great write-up and cool prototype! Love seeing the community push the boundaries of what's possible with the platform.


Wanted to flag two things that are directly relevant to what you're after:


1. Conversation API
We recently announced a Conversation API that will let you make headless requests to the Moveworks assistant programmatically, no Teams or chat UI required. This is essentially the "platform independence" layer you're building toward. You can call it from ServiceNow (or any platform) via REST and receive the same AI-powered responses. Might simplify your integration significantly since you wouldn't need to wire up individual plugins/compound actions on the Moveworks side — you would talk to the assistant directly.
 

2. Ambient Agents
For several of your use cases — incident summarization, solution recommendations, knowledge article generation — Ambient Agents can already handle this today. You can set up an ambient agent that triggers when a new ticket is created (or updated), analyzes it, and posts findings directly as a work note on the ticket. No Teams dependency, no user-initiated interaction required, it all happens automatically in the background. This covers a big chunk of your use cases out of the box.


Between the two, you might find you don't need the custom ServiceNow-to-Moveworks REST plumbing at all.

Would love to hear how these fit into what you're building!

Thanks ​@Kevin Mok , I will give a try to the points you made and shall post back here about the outcomes.


rajeev.saraf
Forum|alt.badge.img+3
  • Author
  • Known Participant
  • February 19, 2026

Hey ​@rajeev.saraf , great write-up and cool prototype! Love seeing the community push the boundaries of what's possible with the platform.


Wanted to flag two things that are directly relevant to what you're after:


1. Conversation API
We recently announced a Conversation API that will let you make headless requests to the Moveworks assistant programmatically, no Teams or chat UI required. This is essentially the "platform independence" layer you're building toward. You can call it from ServiceNow (or any platform) via REST and receive the same AI-powered responses. Might simplify your integration significantly since you wouldn't need to wire up individual plugins/compound actions on the Moveworks side — you would talk to the assistant directly.
 

2. Ambient Agents
For several of your use cases — incident summarization, solution recommendations, knowledge article generation — Ambient Agents can already handle this today. You can set up an ambient agent that triggers when a new ticket is created (or updated), analyzes it, and posts findings directly as a work note on the ticket. No Teams dependency, no user-initiated interaction required, it all happens automatically in the background. This covers a big chunk of your use cases out of the box.


Between the two, you might find you don't need the custom ServiceNow-to-Moveworks REST plumbing at all.

Would love to hear how these fit into what you're building!

HI Kevin, I did not find any way to call listener without REST outbound. can you please help how that can be achieved? 


Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • February 19, 2026

Hey ​@rajeev.saraf - To call a listener, you need to make a REST POST request to the listener. That’s the only way you can trigger it at this time.

Is there any reason you can’t make a REST outbound request from your NOW instance?


rajeev.saraf
Forum|alt.badge.img+3
  • Author
  • Known Participant
  • February 19, 2026

Hi ​@Kevin Mok - I am already doing that by outbound REST message, I was referring to what  you said in the your response.
“Between the two, you might find you don't need the custom ServiceNow-to-Moveworks REST plumbing at all.”


satheesh.kumar1
  • Participating Frequently
  • February 20, 2026

@Kevin Mok, Can ServiceNow send a prompt to reasoning engine and get response back ? 


Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • February 20, 2026

@rajeev.saraf - We may have had some misunderstanding, you still require REST calls, but based on your video and message it seemed like you were trying to build something custom.

 

@satheesh.kumar1 - Not at this time, once the Conversations API is released, it will be possible.


Guruprasad.Marathe
Forum|alt.badge.img+2

which APIs are being used to call moveworks LLM? I thought there is no APIs are exposed by moveworks. please point me to the documentation on how I can call moveworks LLM to get some response via REST APIs.. explain more about how this setup is done


Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • March 5, 2026

@Guruprasad.Marathe - It’s not yet available, that is our Conversations API which is slated for Q2 this year as shown in our roadmap


Guruprasad.Marathe
Forum|alt.badge.img+2

Okay. I knew it was on roadmap, but when I saw a demo, I thought he might be using listener to access LLM with some tricks, when he mentioned below items are used to implement the demoed feature. 

but all those features which he mentioned ServiceNow already provides. with a license off course :) ,  do we require any other license in future to consume moveworks LLM APIs?

 

Moveworks Platform Implementation

The following components were configured within the Moveworks environment to support request handling, orchestration, and secure communication:

  • Listener
  • Plugin
  • Compound action
  • HTTP Actions
  • Credentials

Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • March 5, 2026

About licensing, I don’t have a clear answer for that, it’s outside of my domain. I am sure when we are closer to LPs and GA there will be more information about that.


rajeev.saraf
Forum|alt.badge.img+3
  • Author
  • Known Participant
  • March 6, 2026

which APIs are being used to call moveworks LLM? I thought there is no APIs are exposed by moveworks. please point me to the documentation on how I can call moveworks LLM to get some response via REST APIs.. explain more about how this setup is done

@Guruprasad.Marathe  - It is about calling the Webhook from ServiceNow which invokes a Moveworks plugin → compound action .

this compound action will :

  • get the requirement number from servicenow
  • generate the release note and acceptance criteria .
  • using a post call these generated text will be saved in servicenow record.

eberteo
  • Known Participant
  • March 19, 2026

Hello ​@Kevin Mok 

I’d like to try the Conversation API, you have mentioned. Where can I find the endpoint of this Conversation API  ? - I like the idea of having it as a "platform independence" layer. - Is this LLM internal from Moveworks or the one from NowAssist?

About Ambient Agents — is there an OOB Agent that cover Change Request ticket generation based on a task number the developer work on?.


Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • March 19, 2026

Hey ​@eberteo - The conversations API is not generally available at this time, it’s on our roadmap slated for Q2 of this year. And it’s not NowAssist, this is strictly Moveworks.

 

About the Ambient Agent I am not very sure what you are asking, it would be helpful if you explain your use case in a new post or here.


eberteo
  • Known Participant
  • March 19, 2026

Hey ​@Kevin Mok, sorry about that. I forgot to proofread my previous message. Regarding the Ambient Agents, do you have any link where I can read more information about them?

So I’m looking to automate the change_request table on my ServiceNow instance, this is in relation to the ITSM that my organization follows. Every time we update the system internally we open a record in accordance to the type of Change and in there we explain the ITIL process. I believe this process could be automated by far, instead of investing most of our time in there. 


Kevin Mok
Forum|alt.badge.img+1
  • Community Manager
  • March 19, 2026

That makes sense ​@eberteo 

To get started on it you can read more about them here: System Triggers - I highly recommend using the Ask AI feature on our docsite and also Agent Architect in Agent Studio to help you plan this out.
 

From the sound of it, it should be quite doable.