Cognigy webhook payload missing intent data for CXone Architect routing

We are setting up a custom desktop app using the .NET SDK and need to route calls based on intent data from NICE Cognigy. The idea is to send a webhook from Cognigy to a custom endpoint that then updates the conversation attributes in CXone so our Architect flow can branch correctly. I have the Cognigy side configured to send a POST request with the session data, but the payload arriving at our service seems incomplete. The JSON body only contains the basic session ID and timestamp, completely missing the intent and entities objects that are crucial for the routing logic. Here is the structure we are expecting based on the Cognigy docs:

{
 "sessionId": "abc-123",
 "intent": { "name": "billing_inquiry", "confidence": 0.95 },
 "entities": { "accountNumber": "98765" }
}

But what we actually receive is just:

{
 "sessionId": "abc-123",
 "timestamp": 1678886400000
}

We’ve checked the Cognigy configuration multiple times and the webhook URL is correct. Is there a specific setting in the Cognigy export configuration or a header requirement that triggers the full payload? We are using the standard HTTP action in Cognigy and not seeing any errors on their end, just this truncated data. The CXone side is ready to consume the data once we get it right, but we are stuck on the delivery mechanism.

{
 "sessionId": "{{session.id}}",
 "intent": {
 "name": "{{session.currentIntent.name}}",
 "confidence": "{{session.currentIntent.confidence}}"
 },
 "entities": "{{session.entities}}"
}

Check your Cognigy webhook configuration. The default payload is often stripped down for security or size. You need to explicitly map the intent object in the webhook settings within Cognigy . If you’re just passing {{session}}, you might be hitting a serialization limit or excluding nested objects.

Try mapping the specific fields like session.currentIntent.name directly in the JSON body template. On the CXone side, ensure your REST Proxy action is set to accept application/json and isn’t dropping headers. I’ve seen cases where the Architect flow times out before the payload is fully processed if the endpoint takes too long to respond. Add a debug log in your .NET service to print the raw incoming body. That usually shows if the data is missing at the source or getting dropped in transit.