What are Triggers

Triggers allow you to define situations under which the Moveworks AI Assistant should use a plugin. Moveworks has three types of triggers:

1. Conversational Triggers
2. Event Triggers
3. Scheduled Triggers

Conversational Triggers

How do conversational triggers work?

When you configure a conversational trigger, it makes it possible for your Assistant to present a plugin to users when they ask for it.

Our conversational triggers are built based on a full understanding of the plugin's contents. During configuration, the Agentic Reasoning Engine analyzes the plugin and confirms its understanding with the developer through a contrastive learning experience.

Then, when the user asks your Moveworks Copilot a question, the Manifest Generator takes the following steps:

1. Uses the conversational trigger to filter to the best plugins
2. Uses the plugin title, description, details, & trigger examples to rewrite model-facing plugin descriptions
3. Optimizes the end-user experience with the Agentic Reasoning Engine.

How to write good examples

You should:

• Add triggering examples that span a few diverse examples.
• Never add the same / semantically identical triggering examples as both positive or negative examples for the same plugin.
• Do not add positive examples for vague or generic utterances such as "ticket" or "comment".

Additionally, depending on your situation you should either add positive or negative triggering examples.

Event Triggers

This functionality is coming soon to your Assistant. Please refer to Triggers: Channels and Triggers: Webhooks for the latest updates.

Scheduled Triggers

This functionality is coming soon to your Assistant. Please refer to Triggers: Scheduled Jobs for the latest updates.

Triggering Instructions

Along with triggering examples, you can add triggering instructions to your plugin descriptions. Here are examples:

• Clarify when to use the plugin (e.g. You can only search and query meetings, you cannot do any other read, update, or write actions such as cancel, edit, update, delete.)
• Clarify when to not use the plugin (e.g. Do NOT use this plugin for checking common availability between multiple users, use the "find_availability_between_users" plugin for that purpose. DO NOT attempt to look up someone else's calendar.)
• Clarify how the plugin displays information (e.g. Order records by created date and always use the unique ID as the record key. Please order the sub-fields as: Amount, Created Date, Approver)

Troubleshooting

My plugin is not triggering

There are a number of reasons why your plugin may not trigger.

To isolate the issue, first try to trigger your plugin with one of your configured utterances

Exact match doesn't trigger

If it still doesn't trigger even with the exact match, there are a few reasons why:

1. Plugin not deployed - Plugins take ~10 seconds to deploy to your AI agent. Retry in a minute.
2. Access control failed - Your user might not have access to the plugin. Please double check your Launch Configuration.
3. Conflicting triggering configuration - Your example utterance might be also configured as a negative example, which would prevent it from triggering. Remove it from the Do not trigger list.

Exact match triggers

If the exact match triggers, it is likely that your AI agent doesn't believe your plugin is relevant to the user. There are a few options you have

1. Add more triggering examples.
2. Update your triggering instructions.