Agent Scripting Webhook Payload Structure for ServiceNow Task Creation

General Discussion
1
  • Is it possible to embed the full agent script execution history into a Genesys Cloud Data Action webhook payload destined for a ServiceNow task creation endpoint?
  • The current Architect flow triggers a POST to the ServiceNow REST API upon script completion, but the payload only contains the final disposition code and duration metrics.
  • The ServiceNow integration requires a JSON array of scriptStepId, agentResponse, and timestamp for audit compliance, which seems to exceed the standard Data Action context limitations.
  • Attempting to use the get-conversation-details API call within the flow results in a truncated script log, missing the intermediate branching logic choices made by the agent.
  • The environment is running Genesys Cloud v2023.10 with ServiceNow Washington DC Release, and the MID Server is configured to handle large JSON payloads up to 2MB.
  • The error observed is a 400 Bad Request from ServiceNow citing Missing required field: script_audit_trail in the incoming JSON body.
  • Cross-referencing the Genesys Cloud documentation on Agent Scripting and Data Actions suggests that script execution details are not natively exposed in the standard event payload.
  • Is there a workaround using a custom webhook or an external script to aggregate the script steps before sending to ServiceNow, or is this data simply not accessible via the standard integration paths?
1 Like