We’ve hit a wall with the GetExternalContactAction in our Architect flow. We need to pull customer details based on the inbound caller ID before routing to a skill group. The external system is a simple HTTP endpoint that accepts a phone number and returns a JSON object with customer metadata.
I’ve configured the action to POST to our internal API. The request body is mapped to the incoming interaction’s phone number. When I test the flow in Architect, the action completes without throwing an error, but the response payload is completely empty. No fields are populated in the context data.
Here is the JSON configuration for the external contact action:
{
"url": "https://internal-api.example.com/v1/customer/lookup",
"method": "POST",
"headers": {
"Content-Type": "application/json"
},
"body": "{
\"phoneNumber\": \"{{interaction.from.phoneNumber}}\"
}"
}
The external service returns a 200 OK with valid JSON. I’ve verified this via Postman. The issue seems to be how Architect parses the response. I’ve tried mapping specific fields in the action output configuration, but nothing sticks. Is there a specific format required for the response body? We’re running the latest Architect version. Any ideas on why the payload isn’t sticking?