Skip to main content

Introducing parent interaction id for mw_form in Data API

  • January 29, 2026
  • 0 replies
  • 4 views

vpawar
Forum|alt.badge.img+1

Hello Moveworks Community đź‘‹

We’re excited to announce an enhancement to interaction tracking for live agent connection and ticketing flows in the Data API.

 

What’s new?

We’ve extended “parent_interaction_id” support to mw_form interactions. These forms are in-bot forms used for actions such as:

  • Creating a ticket

  • Connecting to a live agent etc 

With this update, you can now trace the full user journey—from the initial AI Assistant interaction to the form submission that leads to a live agent or ticket creation.

Availability

This enhancement will be available on a going-forward basis starting January 30th 2026.

Interactions created before this date will not include “parent_interaction_id” for mw_form interactions.

Why this matters

This unlocks:

  • Better end-to-end interaction visibility

  • Clearer attribution of which interactions led to a live agent request through the AI Assistant 

 

Updated mw_form interaction object

Below is an example of the updated interaction payload, now including parent_interaction_id:

{
"actor": "user",
"conversation_id": "j1pbqadedlnJ",
"created_time": "2025-06-25T15:54:25.487Z",
"detail": {
"detail": "Live agent chat request"
},
"id": "zzadwercRPG",
"label": "mw_form",
"last_updated_time": "2025-06-26T20:42:19.234Z",
"parent_interaction_id": "{{parent_interaction_id}}",
"platform": "slack",
"type": "INTERACTION_TYPE_UIFORM_SUBMISSION",
"user_id": "{{user_id}}"
}

 

Note : The “change_language” form categorized under the “mw_form” label will not contain parent interaction idÂ