Injecting OTel trace context into Cognigy webhook payloads for CXone routing

We’re wiring up NICE Cognigy to handle dynamic intent-based routing in CXone via webhooks. The problem is the trace context gets lost when the payload hits our Node.js consumer. We’re using the standard /api/v2/analytics/events endpoint to log the event, but the traceparent header isn’t making it through the Cognigy webhook config. Here’s the payload structure we’re sending:

{
 "intent": "billing",
 "traceparent": "00-abc123...-01"
}

Is there a way to inject custom headers into the outbound webhook call from the CXone Architect step?