Quick question about the specific payload structure returned by the predictive_routing:conversation:wrapup event when triggered from a digital channel interaction. We are building a Data Action to push post-interaction survey results and agent wrap-up codes into a custom ServiceNow table via the REST API. The environment is Genesys Cloud EU-West, ServiceNow Madrid 13.1, and we are using the standard HTTP POST action within the Data Action canvas. The issue arises when attempting to map the ‘wrapup_code’ and ‘survey_response’ fields from the webhook payload to the ServiceNow JSON body. The webhook payload contains a nested object under ‘interaction.wrapup_data’, but when we use the token mapper to select these fields, the Data Action execution log shows a 400 Bad Request from ServiceNow with the error message ‘Invalid field value for wrapup_code’. I have verified that the ServiceNow table field allows null values and accepts the string format. When I inspect the raw webhook payload in the GC Admin console, the wrapup_code is present as a string, e.g., “follow_up_required”. However, the Data Action seems to be sending an empty string or null despite the token being populated. I have cross-referenced the Genesys Cloud API documentation for the wrapup event and confirmed that the field is available. Is there a known issue with mapping nested array items or specific wrapup attributes in Data Actions? We have also tried using a JavaScript step to extract the values before the HTTP POST, but the variable scope seems to reset or not pass correctly to the HTTP action body. The MID Server logs show the request body as valid JSON, but ServiceNow rejects it. Any insights on how to properly extract and map these specific wrapup attributes from the digital channel context would be appreciated. We are currently blocked on automating the ticket closure process based on these survey results.