Is it possible to securely transmit ServiceNow instance credentials through a Genesys Cloud Data Action webhook payload without exposing them in the request body logs? We are implementing an automated ticket creation flow where Architect triggers a Data Action to call the ServiceNow REST API endpoint. The integration requires Basic Authentication, but standard Genesys Cloud logging captures the entire outbound HTTP request, including headers and bodies, which creates a significant compliance risk under our security policy. We need a mechanism to inject dynamic credentials at runtime that are masked in the Genesys Cloud audit logs while still being valid for the ServiceNow MID Server.
- Attempted using Genesys Cloud secure variables for the username and password, but the Data Action webhook configuration does not support injecting these variables directly into the Authorization header without them appearing in plain text within the payload definition editor.
- Configured the ServiceNow side to use OAuth Client Credentials flow, but the Genesys Cloud Data Action lacks native support for handling the token exchange sequence required to obtain the bearer token before making the actual ticket creation request.