Introducing agent_id and agent_name fields in Data API Interactions Endpoint (Going Live on 3 November 2026)

What’s changing?

Effective November 3, we’re adding two new fields, agent_name and agent_id, to the detail object returned by the /export/v1/records/interactions endpoint within the Moveworks Data API. These fields identify the assistant that handled each conversation, making it easier to break down usage, trends, and resolution data by Assistant.

If all of your org’s interactions go through the Universal Assistant, agent_name returns “AI Assistant”
If your org has no Productivity Assistants configured, agent_name returns “AI Assistant” by default (for the Universal Assistant).
If a Productivity Assistant is configured (e.g., “Talent Insights”) for your org, interactions routed to it return that assistant’s name.

What you need to know about the impact?

This is a non-breaking change. The new fields are additive, and existing pipelines will continue to work as-is with no action required. To keep your Data API integration resilient to changes like this, please make sure it is built using the Data API integration best practices help doc.

Note: There’s no change to row volume and no backfill. agent_name and agent_id will only be populated for interactions from November 3 onward.

Resources:

If you have any questions or concerns, feel free to comment on this post and our team will get back to you.

Thanks,
Moveworks Analytics team

What’s changing?

What you need to know about the impact?

Resources:

Sign up

If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.

Login or create an account

If you're a Moveworks customer, you can click the SSO button below to login-even if it's your first time. Everyone else can use email or click create an account above to register.