🚧

Limited Preview: Webhook Triggers & Listener

Webhook Triggers and the Webhook Listener are currently in Limited Preview and may change without notice. Access is invite-only. Self-nomination form is here. Production use is approved but may be subject to interruptions or breaking changes.

Learning Objectives

In this Quickstart, you’ll build an Ambient Agent that is triggered on a schedule and notifies you with a weekly risk analysis of purchase requisitions. Along the way you’ll learn how to:

• look up a target user(s) with built in MW.GET_USER_BY_EMAIL_ACTION
• Use built in MW.GENERATE_TEXT_ACTION and the Notify expression.
• Configure a Scheduled Trigger to run a Compound Action on a defined cadence

Prerequisites

• Access to the "Agent Studio" app.

What You'll Build

The plugin you’ll build solves a common, practical problem: proactively surfacing valuable insights to the right person on a reliable cadence.

Before starting to build, we always recommend that you first map out the desired end user experience and the overall building blocks of an Ambient Agent.

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

To get to this experience, the Ambient Agent will consist of one Compound Action

You'll build an end-to-end working Ambient Agent Plugin via these phases:

1. Set up an action.
2. Build the Compound Action, containing three actions and a notify expression.
3. Add the Compound Action to your AI Agent by launching a Plugin.

Let's get started!

Phase 0: Set Up Your Connector

👀

You may be able to skip this phase if you've completed another Agent Studio Quickstart guide. You can skip this phase if:

You have already created a firstname_lastname_moveworks_purple connector. This section will walk you through how to set up your own connector to the Moveworks Purple API (which powers the Actions used in the Quickstart guides), so no need to repeat this step if you've done it before.

In this guide, the purchase requisition data that your Action will access lives behind the Moveworks Purple API Connector. To access this data via your Action, you need to set up a (reusable) connector:

1. Navigate to the App Picker in the top right corner of Agent Studio.
2. Click on "HTTP Connectors", which will take you to another browser tab.

3. Click "Create" in the top right corner.
4. Fill out the following information for your Connector (be sure to replace "firstname" and "lastname" with your corresponding information).

5. Click "Save" on the bottom right corner.

👍

You're now fully ready to start building. On to Phase 1!

Phase 1: Create the HTTP Action to fetch purchase requisitions

1. Navigate to the App Picker in the top right corner. Click on "Agent Studio".

   

2. Navigate to a new HTTP Action.

3. Click "Create".

4. Set the following Title and Description for your Action (be sure to replace "firstname" and "lastname" with your corresponding information).

5. 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 (this represents an endpoint which has one dynamic user email query parameter):
   cURL

   curl -X GET "https://marketplace.moveworks.com/api/purple-suite/erp/purchase-requests/history"

   iii. Click "Import" (your Action should now be auto-populated with details).

6. Add your Connector.
   1. Navigate to the Connector tab.
   2. Select the "Inherit from existing connector" radio button.
   3. Select the Connector you created in Phase 0 from the dropdown (e.g. firstname_lastname_moveworks_purple).

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

   

Phase 2: Create Your Compound Action

You will now create a compound action to handle all the logic of the agent when triggered by the plugin's schedule.

In this phase you will build a compound action with the action you configured to retrieve all purchase requistions, a built in action to lookup the target user's Moveworks profile, and a Notify key to message provide the user the option to retrieve the insights if they select yes it will call a built in action to generate the risk analysis against the purchase requisition data

1. Navigate to a new “Compound Action” in the left nav and then click “Create”.

   
   

2. Set the following title and description for your Compound Action (be sure to replace "first" and "last" with your corresponding information).

   Field	Value
   Title	quickstart_first_last_purchase_requisition_insights_ca
   Description	Sends a message to a user to get insights on purchase requisitions

3. Copy the following expression into the Compound Action Editor and

   1. Replace <your email here> with your actual email on line 9
   2. Replace <your pr action name here> on line 3 with whatever you named the actionfirstname_lastname_get_purchase_requisitions_action from step 1.
   
   
   YAML

   steps:
     - action:
         action_name: <your pr action name here>
         output_key: purchase_requistions
     - action:
         action_name: mw.get_user_by_email
         output_key: user_object
         input_args:
           user_email: '"<your email here>"'
     - notify:
         output_key: notify
         recipient_id: data.user_object.user.id
         message: '"Select yes if you would like to receive an analysis on purchase requisitions for the day"'
         actions:
           - key: yes_option
             label: '"Yes"'
             system_action:
               action_name: mw.generate_text_action
               input_args:
                 model: '"gpt-4.1"'
                 system_prompt: '"Analyze the purchase requistions for the day and risk based on item, dollar amount, and quantity. Callout any specific items that seem over priced or innacurate"'
                 user_input: data.purchase_requistions.$STRINGIFY_JSON()
   

   👉

   Understanding the Compound Action

   This Compound Action executes four actions in sequence, with the output of one step feeding into the next:

   1. firstname_lastname_get_purchase_requisitions_action
      1. Purpose: To identify the notification recipient.
      2. Process: Custom made action you configured in step 1 to call the purple api and retrieve all purchase requisitions.
   2. mw.get_user_by_email (Built-in Action)
      1. Purpose: To identify the notification recipient.
      2. Process: It takes a user's email address (you defined statically) as its input and retrieves that user's unique Moveworks profile ID.
   3. mw.generate_text_action (Built-in Action)
      1. Purpose: To create a polished message for the user and analyze for insights and callout risk.
      2. Process: This action uses an LLM to interpret the raw data in the webhook payload and generate a structured, readable message.
   4. notify (Compound Action Expression)
      1. Purpose: To send the final notification.
      2. Process: This action takes two inputs from the previous steps:
         1. Recipient ID: It uses the user ID that was retrieved by the mw.get_user_by_email action.
         2. Message: It uses the formatted text that was generated by the mw.generate_text_action action.

4. Click "Publish"

👍

All done with Actions!

You're ready to move on — time to create your Plugin and put everything you've built together.

Phase 3: Configure and Launch Your Plugin

This section guides you through adding your Listener and Compound Action to a Plugin. A key step will be configuring the data flow, where you'll specify exactly which fields from the webhook you want to forward to your action.

1. Navigate to a new Plugin (navigate to the library and click "Create").

   

2. Set the following title and description for your Plugin (be sure to replace "first" and "last" with your corresponding information).

   Field	Value to enter
   Title	quickstart_first_last_purchase_requisition_insights_notification
   Description	Sends a message to a user to opt in to recieving purchase requisition insights.

3. In the “Workflow Overview” section click “System” in the Trigger box.

   

   1. Configure your system trigger to connect your Listener in the slide-out pop up with:

      Field Label	Value to enter/select
      Select Trigger Type	Schedule
      Schedule Type	Interval
      Interval Schedule	5 Minutes (or whatever you want for testing) Minimum 1 minute*
      Schedule Settings	Start: Start Immediately after published	Stop: After 1 occurence(s) (recommended to stop so it doesn't keep notifying you)

   

   ii. Click on the "Body" in the "Workflow Overview

   

   1. Configure your system body to connect your compound action to the plugin

      Field label	Value to enter/select
      Select Type	System body
      Select an Action	quickstart_first_last_purchase_requisition_insights_ca (Select yours)

      

4. Click "Publish" to launch your Plugin.

👍

And just like that — you've finished building your Plugin, and now it's ready to use!

Congrats! Your plugin is complete. You should get notified from your AI assistant with a message including a button to receive insights.

Reflecting on this Plugin

The plugin you just created uses several key Agent Studio concepts, from Schedule Triggers to LLM actions to Compound Actions. You've successfully built a plugin that:

• Runs on a cadence on it's own
• *Grabs all the purchase requisitions.
• Processes Processes that data to find insights onto purchase requisitions happening daily.

Awesome work sticking with it!