Does anyone know how to properly ingest Zendesk ticket comment history into Genesys Cloud Architect for IVR personalization? We are currently migrating our support operations from Zendesk Sunshine Conversations to Genesys Cloud. The goal is to use recent ticket interactions to drive IVR menu options. In Zendesk, we relied on the ticket API to pull the latest comment and set a variable for routing. Now, we are trying to replicate this using a Data Lookup block in Architect. We are hitting a 500 Internal Server Error when the flow attempts to query the Zendesk API via a custom connector. The error log shows a timeout after 30 seconds, even though the Zendesk API responds in under 200ms locally. We have verified the OAuth token is valid. The issue seems to stem from how we are structuring the JSON payload for the Data Lookup. We are passing the Zendesk ticket ID as the key. The response from Zendesk is an array of comments. We are trying to extract the body of the most recent comment. In Zendesk, this was straightforward with Liquid tags. In Genesys, we are using a JavaScript block to parse the response before the Data Lookup. However, the flow fails at the Data Lookup stage. We suspect the JSON structure returned by the custom connector is not being parsed correctly by the Architect engine. We have tried flattening the JSON array into a single string, but the error persists. The environment is Genesys Cloud EU region. We are using the latest Architect version. The custom connector is configured with basic authentication. We have checked the firewall settings and confirmed that Genesys Cloud can reach the Zendesk API. We are stuck on this mapping step. It is critical for our migration timeline. We need to map the Zendesk comment content to a Genesys Cloud interaction attribute. This will allow us to trigger specific IVR paths based on customer sentiment. We have reviewed the documentation on Data Lookups and custom connectors. The examples provided do not cover complex JSON arrays from external APIs. We are looking for a working example of mapping Zendesk ticket data to Genesys Cloud IVR attributes. Any advice on structuring the payload or handling the JSON response would be appreciated. We want to ensure that the IVR flow can access the most recent customer comment without causing timeouts or errors. This is a blocker for our digital channel migration. We are eager to move forward but need to resolve this technical hurdle. How do I correctly map Zendesk ticket comment arrays to Genesys Cloud IVR attributes without triggering a 500 error in Architect?