Hey folks,
We’re trying to enrich inbound calls with customer data before routing to an IVR. The plan is to use the GetExternalContactAction data action to hit our internal CRM endpoint and grab some loyalty points and tier info. The endpoint works fine in Postman and curl, returning a 200 with the JSON payload we expect.
The issue is in Architect. When I configure the data action with a GET request to https://api.internal-crm.com/v1/customers?phone={phoneNumber}, the flow just skips the action and moves to the next block. Looking at the flow logs, the data action status is completed, but the response code is 204 No Content. I’ve double-checked the URL and the header mapping. We’re passing the Authorization: Bearer <token> header correctly. The token is valid. I can see the request going out in the network trace, but it seems like Architect is swallowing the response body or failing to parse it.
Here’s the config for the data action:
{
"actionType": "GetExternalContactAction",
"url": "https://api.internal-crm.com/v1/customers?phone={phoneNumber}",
"method": "GET",
"headers": {
"Authorization": "Bearer {{token}}",
"Content-Type": "application/json"
},
"timeout": 5000
}
I’ve tried adding a dummy query param to see if it changes anything, but no luck. The CRM team says the endpoint is returning 200. Is there a specific way we need to structure the response for Architect to accept it? Or maybe a CORS issue that’s being hidden by the 204?
Also, if I switch to a POST with a JSON body, does that change how the parser handles the response? We’ve been stuck on this for two days. Any pointers would be great.