For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
ReferenceGuides
ReferenceGuides
  • Agent Studio
    • Overview
    • Quickstart Guides
    • Core Concepts
      • Assistants, Agents, & Plugins
      • Agentic Automation Engine
      • Conversational Plugins
      • Ambient Agents
      • Data Types
      • Citations
      • Data Bank
      • Structured Data Analysis
    • Conversation Process
    • Actions
    • Connectors
    • System Triggers
    • Agent Architect
    • Cookbooks
    • Development and Testing
    • AI Agent Marketplace
    • Developer Tools
  • Agentic AI
    • LLM Fundamentals
    • The Agentic Reasoning Engine
    • Memory Constructs
    • Conversational Context
    • Guardrails
    • Grounding and Hallucinations
    • Continuous Learning
    • LLMs & SLMs
    • Steerability Tools
    • Multilingual Support
  • Core Platform
    • User Identity
    • Moveworks Agent (On-Prem)
    • Approvals Engine
    • Entity Catalog
    • Moveworks Data Objects
    • Security Information and Event Management (SIEM) Logs Overview
DeveloperAcademyCommunityStatus
On this page
  • Assistants & AI Agents
  • Plugins
  • What type of plugin do I need?
  • User Utterance → Conversational Plugins
  • System Event → Ambient Agents
Agent StudioCore Concepts

Assistants, Agents, & Plugins

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Agentic Automation Engine

The runtime that makes your AI agents enterprise-ready

Next
Built with

Assistants & AI Agents

Moveworks Assistants are agentic systems that can help you accomplish any task: writing emails, managing your calendar, submitting time off, creating expense reports, analyzing CRM data, and more.

Plugins are skills that you give to AI Assistants.

  1. Conversational Plugins are triggered by the Agentic Reasoning Engine. When users chat, Assistants decide which plugins to use to search for information, analyze data, & take action.
  2. Ambient Plugins (aka. Ambient Agents) run in the background. System events & scheduled jobs “trigger” them, but they can also chat with users by sending notifications.

Plugins

You build Plugins in Agent Studio.

What type of plugin do I need?

The first architectural decision is simple: What activates your plugin?

User Utterance → Conversational Plugins

Examples:

  • “Check my PTO balance”
  • “Update the account owner in Salesforce”
  • “Schedule a meeting with my team next week”

Core components:

  • Natural Language Trigger: Auto-generated from plugin name/description
  • Conversation Process: Slots (aka. inputs) required from the user & a set of actions the Assistant should take

Next steps:

  • Read best practices for designing Conversational Plugins.

System Event → Ambient Agents

When to use: Your plugin responds to external system events (webhooks) or runs on a schedule (cron, interval, calendar).

Examples:

  • Daily Customer Feedback Audit (scheduled)
  • Expense Policy Violation Detection (webhook)
  • Time Off Request Approvals (webhook + user notification)

Core components:

  • System Trigger: Webhook listener or schedule
  • Compound Action: Chains API calls without user interaction
  • Conversation Process (optional): If you need to notify or interact with users

Next steps:

  • Read best practices for designing Ambient Agents.