Proactive notifications : Data API

Hello Moveworks Community!
 

We are thrilled to announce a major expansion to the Moveworks Data API. Starting April week 1, 2026, we are evolving the API from a "user-engaged" model to a "system-wide" model by introducing visibility into System-Triggered Events.

Currently, our Data API focuses on conversations where a user has actively participated. But we know that much of the magic of Moveworks happens proactivity—through notifications, ticket interceptions, and channel resolutions. This update brings that proactive power directly into your hands for deep analysis and reporting.

What’s Changing?

We are updating four core entities to include System-Triggered Events (Notifications, Channel/Ticket Interception reach-outs)

Please note that these changes are ADDITIVE in nature and will not break any of your dashboards. However, to make maximum out of this new data you must update your data pipeline.
 

Conversations Entity: The scope is moving from "user-engaged" to all conversations, including those initiated by the system. You will now see records for every notification or interception event the moment they are triggered, regardless of whether the user clicks or responds.
 

Interactions Entity: Every proactive message sent by the bot (like a laptop refresh nudge or a ticket update) will now be visible as a bot-actor interaction.
 

Plugin Calls & Resources: We are now capturing the background work! Any plugin calls triggered by system events (like fetching a ticket for an interception) will be recorded, along with the resources used.
 

We will soon be updating our API documentation to capture the exact updates.

Important Details
 

With great data comes great volume! Here is what you can expect starting week 1 April , 2026:

Note:

• These changes are "forward-looking" only. Historical backfills for these system-triggered events prior to go-live, are not possible.
• Since the volume is expected to grow tremendously, we are implementing a 30 day TTL for Data API.
  • This means that going forward, Data API will allow you to ingest data only up till 30 days back

How to Prepare ?

1. Review Downstream Pipelines: Because of the significant volume increase, ensure your ingestion pipelines and storage are ready for the extra rows.

2. Update Your Dashboards: Start planning how to use the new type and detail fields to report on notification engagement and bot proactivity.

3. Check the Docs: We will be updating our external documentation and release notes as we get closer to the launch date.

We can't wait to see the insights you unlock with this new level of visibility! 🚀