What are plugins?

Plugins are the capabilities of AI agents. You can see our Plugin Library for some examples that you can add to the Moveworks AI Assistant.

How do I build plugins?

To build plugins for AI agents, you need an automation engine that can run plugins. There are two main types of plugins in Moveworks:

• [Recommended] Plugins - these plugins are run by the Agentic Automation Engine.
• Classic Plugins - these plugins require you to use an iPaaS as your automation engine.

🚧

Warning

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).

Plugins

Plugins are run on the Agentic Automation Engine which is designed from its core to build AI agents. 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.

To build plugins, navigate tothe Plugin Workspace in Creator Studio.

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.