Moveworks Setup
Hands-on labs for configuring Moveworks foundational features.
These labs walk you through the end-to-end configuration of a new Moveworks environment. Complete them in order — each lab builds on the previous one.
How to Use These Labs
The Moveworks Setup labs run in order. Lab #0 has a common Moveworks + Okta section, then branches into a track-specific ServiceNow setup page. Labs 1–7 are identical regardless of track.
Step 1 — Set Up Your Moveworks Environment
Start with Lab #0: Environment Setup — Moveworks portal access plus optional Okta SSO. ~45–60 minutes.
Step 2 — Set Up Your ServiceNow Instance (Pick Your Track)
After Lab #0, complete the ServiceNow setup page that matches how you’re taking the labs:
You’re attending a live instructor-led session. Your instructor will provide a ServiceNow Cloud Labs reservation code. Follow this page to claim your Cloud Labs instance.
You’re working through the labs on your own time using your own ServiceNow Personal Developer Instance from developer.servicenow.com. Follow this page to request and configure your PDI.
Step 3 — Complete Labs #1 Through #7
Continue through the remaining labs in order using the table below. Labs marked (Optional) can be skipped depending on your focus area.
Labs #2 and #3 have multi-hour wait times that are separate from the active configuration time. Plan your session accordingly — trigger Lab #2’s user ingestion early so it runs in the background, and complete Lab #3’s configuration well before you need search results available.
Lab #4b update — 2026-04-28. The rewritten Advanced Forms lab is now available. It includes the multi-domain HR catalog setup, a fillability error cheat sheet, and hands-on override/exclusion demos using forms that exist in your training instance. For questions, feedback, or issues, please reply on the community thread.
Agent Studio Quickstart Guides
Once you’ve completed the Moveworks Setup labs, we recommend stepping through the Agent Studio Quickstart series. These guides introduce you to building agents — from simple task automation to ambient agents that trigger on external events.
Before starting: The quickstarts use the Purple API Tool as a mock API backend. Here’s how to set it up:
- Open the Purple API Tool
- Click Create New Session ID — this generates a unique ID and automatically seeds the Feature Requests tab with sample data
- Copy the Session ID and keep it somewhere handy (Notes doc or spreadsheet) — you’ll paste it into cURL commands throughout the quickstarts
The tool has three tabs you’ll encounter across the quickstarts:
- Feature Requests — pre-seeded with sample records when you create your session; used in Quickstarts #1 and #2
- Purchase Requests — starts empty; Quickstart #3 walks you through submitting and reading requests here
- Webhooks — used in Quickstart #5 (requires an external system, covered separately)
Quickstarts 1–4 require only Agent Studio and the Purple API Tool — no external systems needed. Quickstarts 5–7 introduce external dependencies (webhook-capable systems, an LLM service, or an external data source) and are best attempted when those systems are available.