Agent Studio is Moveworks’ platform for building AI-powered plugins that automate business processes. You define what your plugin does — the reasoning engine handles how to execute it at runtime.
This page maps the core building blocks and how they connect. Read it first, then dive into the sections that match what you’re building.
Every plugin follows the same lifecycle: a trigger fires, the reasoning engine selects a plugin, slots are collected, actions execute, and a response is returned.
The diagram below shows how every core concept in Agent Studio relates. The reasoning engine sits at the center — your plugin configuration tells it what to do, and it orchestrates everything else.
R-3824).The hierarchy: Assistants contain Agents, Agents use Plugins. Start here to understand what you’re building.
Plugins triggered by user messages. Covers natural language triggers, slot design, conversation processes, and reasoning instructions.
Plugins triggered by system events (webhooks) or schedules. Run without user interaction.
The runtime that powers your plugins: Plugin Retrieval, Planner, Policies, Slot Resolvers, and the Data Bank.
The centralized data store for plugin execution. Access slot values, action outputs, and system metadata via data.* paths.
The type system for slots and action inputs: strings, numbers, booleans, lists, objects, dates, and structured types.
How to provide source attribution in plugin responses so users can verify the information.
How the reasoning engine interprets and presents tabular data returned by actions.
If you’re new to Agent Studio, read in this order: