Could use a hand troubleshooting this 500 Internal Server Error on /api/v2/integrations/messaging/web/inbound/flows when attempting to map Zendesk macros to Genesys Cloud Web Messaging flows.
The payload structure mirrors the Zendesk workflow logic but the Genesys API rejects it immediately.
Is there a specific JSON schema requirement for the action nodes that differs from the Zendesk macro format?