Skip to main content
Question

Events API deprecation

  • February 10, 2026
  • 1 reply
  • 69 views
J
Forum|alt.badge.img+3

Hi community,

Would it be possible to reconsider deprecating the Events section in the Moveworks Classic Agent Studio? At the moment, it’s no longer possible to create new projects using this functionality.

In my view, the Events API and listeners serve different purposes and are not interchangeable.

The Events API is well suited for simple automation use cases where there are no dynamic variables and minimal complexity - such as sending predefined, global messages. It’s lightweight, easy to configure, and very effective for these scenarios.

Listeners, on the other hand, introduce additional features which is perfect if we want to show buttons and do event processing, but also complexity and they have timeout limitations associated with compound actions.

For these reasons, retaining the Events functionality would still provide value for straightforward use cases.

Thank you for considering this.

jpasd96

    1 reply

    Kevin Mok
    Forum|alt.badge.img+2
    • Kevin Mok
    • Community Manager
    • February 19, 2026

    Hey ​@João Durand, appreciate you raising this.

    You're right that the Events API was simpler for fire-and-forget messaging. Send a POST, pass a list of emails and a message, done. For that specific use case, it worked.

     

    Here's the thing, though: we kept running into the wall where teams would send a message and then need the user to actually do something with it. No buttons, no follow-up actions, nothing. So people started hacking around it with event-triggered paths, which technically worked but was rigid and hard to maintain. We heard that feedback a lot.


    Listeners are more involved to set up. But they solve the problem that Events couldn't: what happens after the message lands. You can wire up webhooks with proper auth, trigger compound actions that run background jobs, notify users with buttons that kick off conversations, or hit APIs. One listener can handle webhooks correctly which Events never supported.


    We made the conscious call to trade simplicity for flexibility. For a "send this predefined message to these people" scenario, it's more set up than before. But the moment you need anything beyond that, you're already in the right place instead of hitting a dead end and having to rebuild.


    Listeners are the path forward, and we're continuing to invest in making them easier to work with.

      Terms & ConditionsCookie settingsAccessibility statement