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
      • Purple Suite Setup
      • Quickstart #1: Build Your First Plugin
      • Quickstart #2: Slots & Resolvers
      • Quickstart #3: Build a Plugin That Follows a Process
      • Quickstart #4: Structured Data Analysis (SDA)
      • Quickstart #5: Notification Ambient Agent
      • Quickstart #6: Expense Approval Ambient Agent
      • Quickstart #7: Scheduled Trigger Ambient Agent
      • Purple API Tool
    • Core Concepts
    • 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
  • Learning Objectives
  • Prerequisites
  • What you’ll build
  • Phase 0: Set Up the Purple Suite
  • Phase 1A: Set up your “Get Historical Purchases” Action
  • Phase 1B: Set up your “Submit Purchase Request” Action
  • Phase 2: Build your Conversational Process
  • Phase 3: Launch a Plugin
  • Reflecting on this Plugin
Agent StudioQuickstart Guides

Quickstart #3: Build a Plugin That Follows a Process

Build a purchase-request submission plugin with multiple slots, activities, and a decision policy.

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

Quickstart #4: Structured Data Analysis (SDA)

Next
Built with

Learning Objectives

This Quickstart guide walks you through building a plugin that helps users submit purchase requests. The plugin follows a multi-step process: collect details, classify the request, and either submit it or send the user down a different path. You’ll learn how to:

  • Use a Decision Policy to control branching logic in a Conversational Process.
  • Use multiple types of Activities in a Conversational Process to handle different tasks.
  • Design a plugin that uses several Slots with simple Validation Policies.

Prerequisites

  1. Access to the “Agent Studio” App.
  2. Completed Quickstart #1: Build Your First Plugin.

What you’ll build

You’ll build a purchase request submission plugin. It asks the user for details about the purchase request they want to submit, compares the details against historical purchase requests, and either submits it if it can be classified as “OpEx” or rejects it if it’s classified as “CapEx”.

Here is an example of the end-user experience we hope to enable:

To build this, here’s one way to decompose the work into a Conversational Process, consisting of a few Activities (both Action-based and Content-based), a Decision Policy, and a few Slots to power the data needed in this process:

In this guide, you’ll work your way through these main phases:

  1. Set up 2 HTTP Actions: one to fetch historical purchase requests, and another to submit a new one.
  2. Build the Conversational Process, complete with 4 Slots, 5 different Activities, and 1 Decision Policy, as illustrated above.
  3. Add the Conversational Process to your AI Assistant by launching a Plugin.

Let’s get started!

Phase 0: Set Up the Purple Suite

Already set up?

If you’ve already completed the Purple Suite Setup and have your connector configured, skip to Phase 1A.

Follow the Purple Suite Setup guide to:

  1. Create a Purple Suite instance at marketplace.moveworks.com/purple-suite
  2. Get your Instance ID and API Token (PAT)
  3. Set up a connector in Agent Studio with API Key auth

Phase 1A: Set up your “Get Historical Purchases” Action

️ Import building notes if you are using the Moveworks Developer Labs environment
  1. If you are working in a Moveworks lab environment, name anything you save (Plugin, Action, Data Type, etc.) with <fullname>_<descriptive_name>
    1. For example: lucasrollo_Submit_PTO_Action
  2. When launching your Plugin, make sure to only launch to yourself! You can do this by going to Your Plugin > Launch Configuration > Allow Selected Users > the email on your credential card

Let’s first set up an HTTP Action that will retrieve historical purchase requests. This Action doesn’t require any dynamic inputs, and will just query an external system for a list of purchase requests.

1

Navigate to Agent Studio

Navigate to the App Picker in the top right corner. Click on “Agent Studio”.

2

Create a new HTTP Action

Navigate to a new HTTP Action.

3

Set the title and description

Set the following title and description for your Action (be sure to replace “firstname” and “lastname” with your corresponding information).

FieldValue to enter (replace “firstname” & “lastname” with your info)
Titlefirstname_lastname_get_historical_purchases
DescriptionFetches a list of historical purchase requests
4

Import the API details

Enter the details of your API:

  1. Click on the “Import” icon to the right of the “TEST” button.

  2. Paste the following cURL command:

    $curl -X GET "https://marketplace.moveworks.com/api/purple-suite/erp/purchase_orders" \
    >  -H "Authorization: Bearer YOUR_PAT" \
    >  -H "X-Instance-ID: YOUR_INSTANCE_ID"

  3. Click “Import” (your Action should now be auto-populated with details).

5

Add your connector

Navigate to the “Connector” tab, and select your existing Moveworks Purple Connector (set up in Phase 0).

6

Test your action

Test your Action:

  1. Click on the “TEST” icon (to the right of the endpoint URL definition).

  2. Inspect the Console to verify that you receive a successful response:

7

Publish

Hit “Publish”.

You've just set up 1 out of 2 custom Actions needed for this process!

This Action will fetch the critical history of past purchase requests (that later you’ll compare a user’s new request against). Next up: setting up an action to actually submit new purchase requests.

Phase 1B: Set up your “Submit Purchase Request” Action

️ Import building notes if you are using the Moveworks Developer Labs environment
  1. If you are working in a Moveworks lab environment, name anything you save (Plugin, Action, Data Type, etc.) with <fullname>_<descriptive_name>
    1. For example: lucasrollo_Submit_PTO_Action
  2. When launching your Plugin, make sure to only launch to yourself! You can do this by going to Your Plugin > Launch Configuration > Allow Selected Users > the email on your credential card

The next (and final) Action to set up will add a new purchase request object (and will actually update the purchase record database in your instance!). This Action will require three dynamic inputs: item_name, quantity, and justification.

1

Create a new HTTP Action

Navigate to a new HTTP Action.

2

Set the title and description

Set the following title and description for your Action (be sure to replace “firstname” and “lastname” with your corresponding information).

FieldValue to enter (replace “firstname” & “lastname” with your info)
Titlefirstname_lastname_submit_purchase_request
DescriptionSubmits a new purchase request to Procurement
3

Import the API details

Enter the details of your API:

  1. Click on the import button to the right of the “TEST” button.

  2. Paste the following cURL command:

    $curl -X POST "https://marketplace.moveworks.com/api/purple-suite/erp/purchase_orders" \
    >  -H "Authorization: Bearer YOUR_PAT" \
    >  -H "X-Instance-ID: YOUR_INSTANCE_ID" \
    >  -H "Content-Type: application/json" \
    >  -d '{
    >      "vendor": "{{item_name}}",
    >      "totalAmount": 1200.00,
    >      "lineItems": {{quantity}},
    >      "status": "draft",
    >      "currency": "USD"
    >  }'

  3. Click “Import” (your Action should now be auto-populated with details).

4

Add your connector

Navigate to the “Connector” tab, and select your existing Moveworks Purple Connector (set up in Phase 0).

5

Define input arguments

Define 3 formal input arguments to represent the “item name”, and “quantity”, and “business justification” inputs that this Action requires:

  1. Click on the “Input Args” button near the top right corner.

  2. Click “Create New” in the “Input Arguments” pop up.

  3. Fill out the following details for your item_name argument:

    Field labelValue to enter/select
    Argument Nameitem_name
    Data TypeSelect “string”
    Example Valuepen
    DescriptionThe name of the item to be purchased
    RequiredCheck the box

  4. Hit “Save”.

  5. Click “Create New” again in the “Input Arguments” pop up.

  6. Fill out the following details for your quantity argument:

    Field labelValue to enter/select
    Argument Namequantity
    Data TypeSelect “Number”
    Example Value20
    DescriptionThe quantity of the item in the purchase request
    RequiredCheck the box

  7. Hit “Save”.

  8. Click “Create New” again in the “Input Arguments” pop up.

  9. Fill out the following details for your justification argument:

    Field labelValue to enter/select
    Argument Namejustification
    Data TypeSelect “string”
    Example ValueNeeded to refill supply closet
    DescriptionThe business justification for the item(s) in the purchase request
    RequiredCheck the box

  10. Hit “Save” and hit the “X” icon to close this “Input Arguments” pop up.

6

Test your action

Test your Action:

  1. Click on the “TEST” icon (to the right of the endpoint URL definition).

  2. Inspect the Console to verify that you receive a successful response:

7

Publish

Hit “Publish”.

Nice, your Actions are all set up and ready to go!

Time to construct your Conversational Process.

Phase 2: Build your Conversational Process

️ Import building notes if you are using the Moveworks Developer Labs environment
  1. If you are working in a Moveworks lab environment, name anything you save (Plugin, Action, Data Type, etc.) with <fullname>_<descriptive_name>
    1. For example: lucasrollo_Submit_PTO_Action
  2. When launching your Plugin, make sure to only launch to yourself! You can do this by going to Your Plugin > Launch Configuration > Allow Selected Users > the email on your credential card

Here’s a reminder of the bird’s eye view for this Submit Procurement Purchase Request Conversational Process:

Let’s build it!

1

Create a new Conversational Process

Navigate to a new Conversational Process (navigate to the library and click “Create”).

2

Set the title and description

Set the following title and description for your Conversational Process (be sure to replace “firstname” and “lastname” with your corresponding information).

FieldValue to enter (replace “firstname” & “lastname” with your info)
Titlefirstname_lastname_support_procurement_purchases_process
DescriptionThis will help users submit a Procurement purchase request.
3

Add the four Slots

Add the FOUR Slots that this process will need: item_name, quantity, business_justification, and is_purchase_for_organization_acknowledgement. 📖 Learn more about Slots.

  1. Click on the “Slots” button near the top right corner of the editor.

  2. Click “Create New” in the “Slots” pop up.

  3. Fill out the following details for your first item_name Slot:

    Field labelValue to enter/select
    Nameitem_name
    Data TypeSelect “string”
    Slot DescriptionThe name of the item that the user wants to purchase.
    Slot Validation PolicyLeave blank
    Slot Validation DescriptionLeave blank
    Slot Inference PolicyLeave as is (Infer slot value if available)

  4. Hit “Save” (scroll to the bottom of the popup).

  5. Click “Create New” again in the “Slots” pop up to build your second Slot.

  6. Fill out the following details for your business_justification Slot:

    Field labelValue to enter/select
    Namebusiness_justification
    Data TypeSelect “string”
    Slot DescriptionA justification from the user on why this purchase is necessary.
    Slot Validation PolicyLeave blank
    Slot Validation DescriptionLeave blank
    Slot Inference PolicyLeave as is (Infer slot value if available)

  7. Hit “Save” (scroll to the bottom of the popup).

  8. Click “Create New” again in the “Slots” pop up to build your third Slot.

  9. Fill out the following details for your quantity Slot:

    Field labelValue to enter/select
    Namequantity
    Data TypeSelect “number”
    Slot DescriptionThe number of units of the item that the user wants to purchase.
    Slot Validation Policyvalue > 0
    Slot Validation DescriptionThe quantity for the item in the purchase request must be greater than zero
    Slot Inference PolicyLeave as is (Infer slot value if available)

  10. Hit “Save” (scroll to the bottom of the popup).

  11. Click “Create New” again in the “Slots” pop up to build your fourth and final Slot.

  12. Fill out the following details for your is_purchase_for_organization_acknowledgement Slot:

    Field labelValue to enter/select
    Nameis_purchase_for_organization_acknowledgement
    Data TypeSelect “boolean”
    Slot DescriptionAn explicit acknowledgement from the user that this purchase is for the organization and not for personal use.
    Slot Validation Policyvalue == TRUE
    Slot Validation DescriptionThe user must explicitly acknowledge "yes" to indicate that this purchase is intended for the organization and not for personal use.
    Slot Inference PolicySelect “Always prompt the user”

  13. Hit “Save” (scroll to the bottom of the popup) and hit the “X” icon to close this “Slots” pop up.

4

Build the first Action Activity

Build the first Action Activity that fetch a list of historical purchase requests that the process will later compare against. 📖 Learn more about Activities.

  1. Click on the ”+ Add a block to your process” button in the main section of the editor.

  2. Click on “Action Activity”.

  3. Fill out the following details for your Action Activity, which simply hooks up the Action you created to this Action Activity:

    Field label

    Value to enter/select

    Action

    *Select thefirstname_lastname_get_historical_purchases Action that you built in Phase 1A *

    Required Slots

    Leave blank (no Slots are needed as input to this Activity)

    Input mapping

    Leave blank (no inputs to map to)

    Output Mapping (“.dot_walk_here” box)

    Leave blank (output is fine as is)

    Output Key

    historical_purchases

    Confirmation Policy

    Leave unchecked

5

Build the second Action Activity

Build the second Action Activity, which will utilize a Built-in Action that can generate an output according to a natural language prompt. 📖 Learn more about the Built-in Generate Text Action.

  1. Click on the ”+” icon below the previous Activity in the main section of the Conversational Process Editor.

  2. Click on “Action Activity”.

  3. Fill out the following details for your Action Activity, which mostly involves constructing a templated prompt to the Action, and mapping the predicted purchase request classification out of the model’s response:

    Field label

    Value to enter/select

    Action

    Select themw.generate_text_action Built-in Action

    Required Slots

    Select 1 slot:item_name

    Input mapping (2 fields mapped)

    system_prompt: $CONCAT(["'Take the '", data.item_name, "' and compare it against the '", data.historical_purchases.$STRINGIFY_JSON(), "' to determine its Opex or Capex classification. Only output Opex or Capex'"], "") user_input: "' '"

    Output Mapping (“.dot_walk_here” box)

    .openai_chat_completions_response.choices[0].message.content

    Output Key

    pr_classification

    Confirmation Policy

    Check the “Require consent from the user” box

6

Build the Decision Policy

Build your first Decision Policy, which will execute after the already configured 2 Activity blocks. This policy will allow the Process to branch its execution depending on the pr_classification returned by the generate text Action Activity. 📖 Learn more about Decision Policies.

  1. Click on the ”+” square icon below the second generate text Activity in the main section of the Conversational Process Editor.

  2. Click on “Decision Policy”. (No need to input anything in the panel that appears on the right).

  3. Increment the number of Cases by clicking on the ”+” button to the right of the words “1 case”.

  4. Click on the first Case entry under the Decision Policy and enter the below DSL rule in the panel that appears on the right:

    DSL
    data.pr_classification.$LOWERCASE() == "opex"

  5. Click on the second Case entry under the Decision Policy and enter the below DSL rule in the panel that appears on the right:

    data.pr_classification.$LOWERCASE() == "capex"
7

Create the OpEx Action Activity

Create the Action Activity that will execute under the first Decision Policy Case (pr_classification is opex).

  1. Click on the ”+” icon below the first Case entry under the Decision Policy.

  2. Select “Action Activity”.

  3. Fill out the following details for your Action Activity, which will connect your slots to the input(s) of the HTTP Action (and mapping the result of the Action back to the Conversational Process).

    Field label

    Value to enter/select

    Action

    *Select thefirstname_lastname_submit_purchase_request Action that you built in Phase 1B *

    Required Slots

    Select all 4 Slots:item_name, quantity, business_justification, and is_purchase_for_organization_acknowledgement

    Input mapping (3 fields mapped)

    item_name: data.item_name justification: data.business_justification quantity: data.quantity

    Output Mapping (“.dot_walk_here” box)

    Leave blank (output is fine as is)

    Output Key

    submitted_pr_result

    Confirmation Policy

    Check the “Require consent from the user” box

    1. Note that even though is_purchase_for_organization_acknowledgement is not technically needed to invoke the submit purchase request action, marking it as a required Slot for this Activity ensures that the AI Assistant fills the Slot before executing this Activity.
8

Create the CapEx Content Activity

Create the Content Activity that will execute under the second Decision Policy Case (pr_classification is capex).

  1. Click on the ”+” icon below the second Case entry under the Decision Policy.

  2. Select “Content Activity” this time.

  3. Keep the “Content Type” set to “Text”.

  4. Paste the following text content (which will share text instructions with the user on how to submit purchase requests that fall under CapEx).

    Text Content
    This request falls under CapEx. Please visit <a href="https://www.google.com">CapEx Submission Portal</a> to submit your request.
9

Create the default Content Activity

Create the Content Activity that will execute under the default branch (when pr_classification somehow is neither opex nor capex).

  1. Click on the ”+” icon below the second Case entry under the Decision Policy.
  2. Select “Content Activity” again.
  3. Keep the “Content Type” set to “Text”.
  4. Paste the following text content (which will share text instructions with the user on how to submit purchase requests that fall under CapEx).
    Text Content
    Unfortunately, this purchase request could not get categorized, so it was not submitted. Please feel free to try submitting another request.
10

Validate

Click “Validate”. If everything went well so far, the Console (bottom of the editor) will say “Validation successful”.

  1. 💡Pro-tip: You can also use the following hotkeys to validate without pressing the button:

    On a MacOS machineOn a Windows machine
    Cmd + Shift + VCtrl + Shift + V
11

Publish

Click “Publish”, review details, and Click “Publish” once again.

Congratulations! You've just built the main part of this Plugin: the Conversational Process.

Way to stick through all the steps! We’re ready for the last phase: now you’ll launch a Plugin — this packages the Conversational Process into a tool that your AI Agent can use directly.

Phase 3: Launch a Plugin

️ Import building notes if you are using the Moveworks Developer Labs environment
  1. If you are working in a Moveworks lab environment, name anything you save (Plugin, Action, Data Type, etc.) with <fullname>_<descriptive_name>
    1. For example: lucasrollo_Submit_PTO_Action
  2. When launching your Plugin, make sure to only launch to yourself! You can do this by going to Your Plugin > Launch Configuration > Allow Selected Users > the email on your credential card

It’s finally time to add your Conversational Process to a Plugin, where you can control the Triggering scenarios of your Plugin and specify which end users are allowed to use your Plugin.

1

Create a new Plugin

Navigate to a new Plugin (navigate to the library and click “Create”).

2

Set the title and description

Set the following title and description for your Plugin (be sure to replace “firstname” and “lastname” with your corresponding information).

FieldValue to enter (replace “firstname” & “lastname” with your info)
Titlefirstname_lastname_support_procurement_purchases
DescriptionThis will help users submit a Procurement purchase request. This first compares the name of the purchase request that the user wants to submit against a list of historical purchase requests to determine whether the request is classified as "OpEx" or "CapEx". Depending on the classification, it will either submit the purchase request directly for the user or give the user more information on how to proceed.
3

Define a Conversational Trigger

Define a Conversational Trigger. 📖 Learn more about Natural Language Triggers.

  1. Click on “No triggers configured”.

  2. In the panel that appears on the right, either:

    1. Approve (click “Trigger”) 5 of the auto-generated suggested positive examples, or

    2. Add the following recommended utterances:

      Utterances to add
      submit purchase request
      how can i submit a purchase request to procurement?
      I need to order 100 pens for the office
      I need to submit a purchase request for a laptop
      Can I submit a purchase order?
4

Choose your Conversational Process

Choose your Conversational Process (the one you built in Phase 2).

  1. Click on “No body configured”.
  2. In the panel that appears on the right, search for and select the Conversational Process that you built in Phase 2 (should be named firstname_lastname_support_procurement_purchases_process)
5

Define your Launch Configuration

Define your Launch Configuration.

  1. Navigate to the “Launch Configuration” tab.

  2. In the Input field under “Allow selected users”, enter your email (or multiple emails using commas to separate the email addresses).

6

Publish

Click “Publish” to launch your Plugin.

Woohoo! You've finished building your Plugin — time to try it out!

Use one of your triggering examples (e.g. “submit purchase request”) to access the Plugin in conversation. Try refreshing your submitted purchase requests tab in your Purple Suite session to see the updates take effect in real time!

Reflecting on this Plugin

The plugin you just built contains a plethora of Agent Studio concepts, from different Activity types to Decision Policies. There’s a lot it had to take care of:

  • Retrieve historical purchases from an external source.
  • Perform classification on the fly to figure out how to categorize the user’s intended purchase.
  • Make an informed decision on the best way to support the request, depending on the predicted classification.
  • Collect critical information that’s needed for submitting a purchase request.
  • Executes for the right users at the right moments via Triggering and Launch configurations you’ve set up.

Congratulations on building this powerful plugin — it’s now ready to help support users with their procurement purchase needs!

Next step: Test your plugin. See our Testing & Error Handling guide for how to test, debug, and handle errors in production.