Looking for advice on mapping a nested JSON response from an external REST call within a Genesys Cloud Architect flow. I am provisioning the flow via Pulumi TypeScript, but the runtime behavior is the issue. The Data Action successfully hits the endpoint, but the variable mapping seems to ignore the inner object structure. Here is the Data Action definition I am pushing:
{
"id": "ext-customer-lookup",
"type": "restApiCall",
"name": "Get Customer Details",
"request": {
"url": "https://api.external.com/v1/customer/\${customer.id}",
"method": "GET",
"headers": {
"Authorization": "Bearer \${auth.token}"
}
},
"responseMappings": [
{
"sourceField": "profile.name",
"targetVariable": "customerFullName"
},
{
"sourceField": "profile.preferences.locale",
"targetVariable": "userLocale"
}
]
}
The external API returns a 200 OK with this payload:
{
"status": "success",
"profile": {
"name": "John Doe",
"preferences": {
"locale": "en-GB"
}
}
}
When I trace the flow in Architect, customerFullName gets populated correctly as “John Doe”. However, userLocale remains null. I have verified the API response multiple times using Postman, and the JSON structure is consistent. I suspect the dot notation in the sourceField for nested objects might be handled differently in the latest Architect runtime compared to what the documentation suggests. I am running this in the UK South region.
Has anyone encountered issues with deep nesting in Data Action response mappings? Should I be flattening the JSON in a Studio snippet first, or is there a specific syntax for accessing nested properties in the responseMappings array? Any working examples of mapping deeply nested fields would be appreciated.