ServiceNow Flows & Actions in Moveworks
What is ServiceNow Flows & Actions in Moveworks?
ServiceNow customers have built years—often decades—of business logic and automation using Flow Designer, Workflow Studio, actions, and subflows. This capability makes those existing ServiceNow automations available as execution tools for Moveworks agents.
Rather than rebuilding the same logic in a separate system, teams can expose selected ServiceNow actions and subflows through a ServiceNow MCP server. The Moveworks Assistant can then invoke those tools as part of a conversational request, while the underlying automation continues to run in ServiceNow.
Availability
This capability depends on MCP Workspace, which will provide the Moveworks-side experience for configuring and managing MCP connections and tools.
How it works
- An administrator configures an MCP server in ServiceNow using MCP Platform Manager.
- The administrator registers the appropriate Flow Designer actions and subflows as MCP tools.
- Moveworks connects to the ServiceNow MCP server and makes the approved tools available to its agents.
- When a user's request requires an action, the Moveworks agent invokes the relevant ServiceNow tool and presents the result in the conversation.
ServiceNow supports creating MCP tools from both Flow Designer actions and subflows.
What can users do?
The available experiences depend on the automations each organization chooses to expose. Example requests could include:
- “Register Tempo Analytics as a new business application.”
- “Start the employee offboarding workflow for this contractor.”
- “Request approval to add this application to the software catalog.”
- “Provision the standard development environment for my new engineer.”
- “Run the approved remediation flow for this configuration item.”
- “Create the application record and route it to the correct owner for approval.”
For example, an existing ServiceNow flow could check whether an application already exists, create or update the appropriate records, route an approval request, and notify the relevant teams. The employee initiates the request in Moveworks, while ServiceNow remains the system executing the established workflow.
Why it matters
- Reuse existing investments: Extend ServiceNow automations your organization has already designed, governed, and tested.
- Avoid duplicate development: Make existing actions and subflows available to Moveworks agents instead of recreating their logic elsewhere.
- Bring execution into conversation: Let employees initiate complex workflows using natural language in the Moveworks Assistant.
- Keep administration in ServiceNow: ServiceNow administrators choose which automations become MCP tools and how those tools are configured.
Configuration and requirements
Administrators will configure the ServiceNow MCP server and select the actions and subflows that should be exposed as tools. Individual tools must meet ServiceNow's compatibility, input/output, and access-control requirements.
This capability uses MCP to connect Moveworks agents to the tools configured in the customer's ServiceNow instance.