Ambient Agents: Webhooks

​@Ajay Merchia this is a feature that we are quite excited about as we would prefer to avoid leveraging iPaaS for various security reasons. Is this still planned for limited preview in Q1 of 2025?

Hey ​@Nick Barber, we are still actively prioritizing this and planning for our Q1 2025, but it’ll be a variation where you can initiate the job via a webhook rather than a scheduled trigger. 

We want to make sure we address some of the concerns folks have raised from how event-triggered paths worked, and make that a stronger foundation to build scheduled jobs on top of.

Any update on this? When can we expect Event Triggers in plugins to be available?

Ei team, is there an update on this? thanks

Also looking for an update, this looks like a hot topic!!

Hi ​@chetan.bhagat, ​@ferdinand.codizal, & ​@hundleymf! Thanks for checking in on this. I checked with the team and the plan is still to have this available for limited preview in Q2. Stay tuned, we will update on this thread and also on our limited preview page. 

Really looking forward for this functionality!!!

Looking forward to this one for sure. We are waiting to scale up using Webhooks!

Hi team! This is now in Limited Preview, which can be found HERE.

Some more details on limited preview for webhooks:

Core capabilities during limited preview

1. Create a listener

A listener is how your agent subscribes to external events. It’s where you tell Moveworks what system to listen to (like Salesforce, DocuSign, or Asana) and what types of events to expect.

Once set up, the system will start sending live event data to Moveworks automatically. You can name, manage and delete your listeners.

2. Filter events

Apps generate mountains of event data — not every event coming from a system is important to you. Filtering let’s you apply rules at the listener-level to ignore/reject noisy events upfront.

3. Trigger actions

Once an event passes the filter, Moveworks can then trigger one (or more) actions which could include notifications to users, approvals, or be fully behind the scenes. Actions can include:

- Send a reminder (e.g. complete your new employee training)
- Kick off an approval (e.g. for expense or access requests)
- Call an external API (e.g. update a ticket, trigger an automation)

4. See what happened (aka logs)

Moveworks logs every incoming event and what action was taken (or not taken). Devs can trace what triggered an automation, inspect the raw event data, and debug if something didn’t work as expected.

What are the limitations and caveats to be aware of?

- Scheduled triggers or pollers are not included in limited preview. Those are coming soon though!.
- Can both a system trigger and a conversational trigger trigger a single plug-in? No. A plugin cannot be triggered by both a system trigger and a conversational trigger.

Interesting to see how you’re making it!

Fantastic! Can we leverage this for publishing event based knowledge ingestion?