What are AI agents & plugins?

AI agents are capable of carrying out tasks on behalf of a user. There are thousands of repetitive tasks that you can automate when you build AI agents (see our Plugin Library for inspiration).

To build an AI agent, you need an Reasoning Engine (powered by LLMs) and Actions (which the agent can execute). When building on the Moveworks Platform, you use the Moveworks Reasoning Engine as your LLM, and the Agentic Automation Engine is where you build your Actions (called "Plugins" in our platform).

📘

In Moveworks, there is ONE AI agent. You build plugins.

The main Moveworks Copilot is your AI agent and it has access to all your data & workflows across business systems through its plugins. We build & manage a powerful reasoning architecture, so you only have to build half the AI agent (through plugins).

As a result, you get a single AI agent for every business system. You eliminate the application sprawl problem. Your employees don't go from juggling hundreds of apps, to hundreds of AI agents. They just need one: Moveworks.

How do I build plugins?

Agentic Automation Engine Plugins

To build plugins for your AI agents, you need an automation platform. Traditional iPaaS and middleware are not meant for building AI agents. They were designed for connecting APIs to other APIs, so they struggle to connect AI agents (which use language) to APIs (which expect well-formed data).

The purpose of the Agentic Automation Engine is to give developers a unified platform that's designed from the core to build these automations. To learn more about the core capabilities that power our Agentic Automation Engine, and how it differs from traditional iPaaS & middleware, read our white paper.

The Plugin Workspace is where you go in Creator Studio to build on the new Agentic Automation Engine.

When you build a plugin, there are a few key pieces required.

• Triggers - The trigger for the plugin. Read more about our Manifest Generator.
• Slots - The inputs from the user the plugin needs. Read more about our Slot Resolvers.
• Policies - The rules the plugin follows deterministically. Read more about our Policy Validators.
• Execution Body - The automations the plugin executes. Read more about our Action Orchestrator.

Classic Plugins (Paths, Queries, & Events)

Prior to the release of the Agentic Automation Engine, we introduced our Classic Workspaces: Paths, Queries, and Events, which used traditional iPaaS tools as the automation engine for plugins.

While not as powerful, you can still choose to build with them. To learn more about the Classic Workspaces, please visit our classic documentation.

What counts as a plugin?

In Creator Studio, one plugin has one launch configuration. This applies to both plugins built on the Agentic Automation Engine, as well as classic plugins like Paths, Queries, Events, Event-triggered Paths, & Query-triggered paths.

They all count as a single plugin. We referred to these as "use cases" on our Classic architecture.