Hey everyone, I’ve run into a really strange issue with the integration between Genesys Cloud Architect NLU nodes and our ServiceNow incident creation flow. The environment is Genesys Cloud Release 2024-12 (v13.2) deployed in AWS London, interacting with a ServiceNow instance via a REST API webhook. The specific issue arises when the NLU node returns a confidence score below the configured threshold of 0.85. According to the documentation, the intent.confidence field should be passed as a decimal, but the payload sent to ServiceNow is being interpreted as a string, causing the u_gc_confidence field validation to fail with a 422 Unprocessable Entity error. The webhook payload structure includes "u_gc_confidence": "0.72" instead of 0.72. Despite using a Data Action to format the JSON, the string conversion persists. The ServiceNow endpoint api/now/table/incident rejects the string value for the decimal field. We have verified the Data Action configuration in Genesys Cloud, ensuring the intent.confidence is mapped correctly. However, the issue seems to stem from how the webhook node serializes the payload before transmission. The error logs in ServiceNow show: Error: Value '0.72' is not a valid number for field u_gc_confidence. We are trying to understand if this is a serialization bug in the Genesys Cloud webhook execution node or if there is a specific configuration setting in the Data Action to enforce numeric formatting. The Architect flow uses a standard HTTP POST request with headers Content-Type: application/json and Authorization: Basic <base64>. The issue is intermittent, occurring only when the confidence score is below 0.9. Any insights on forcing numeric serialization in the webhook payload would be appreciated. The current workaround involves a post-processing script in ServiceNow, but this is not ideal for high-volume scenarios.