GetExternalContactAction 404 on valid phone number lookup

Architect & Flows
1

The Architect GetExternalContactAction returns a 404 Not Found even though the number exists in our CRM. The request payload is standard:

{
 "lookupKey": "phone",
 "lookupValue": "+5511999999999"
}

The external service endpoint is reachable via Postman. The action configuration points to the correct URL. The timeout is set to 5000ms. Any idea why Architect drops the request before it hits the proxy?

2

Check the HTTP verb setting in the Data Action configuration. The default for GetExternalContactAction is often GET, but if your CRM endpoint expects a POST with that JSON body, Architect will send a GET request with query parameters instead. That mismatch causes the 404 if the server doesn’t handle GET for that specific route.

Try switching the method to POST in the Data Action editor. Also, verify the Content-Type header is set to application/json. If the CRM returns a 404 on a POST without the correct header, it might be dropping it early.

Here is the corrected Data Action config :

{
 "method": "POST",
 "headers": {
 "Content-Type": "application/json"
 },
 "body": "{\n \"lookupKey\": \"phone\",\n \"lookupValue\": \"{{lookupValue}}\"\n}"
}

If that doesn’t fix it, check the network logs in Architect. Look for the actual request sent. Sometimes the lookupKey isn’t being interpolated correctly if the variable source is wrong. Ensure lookupValue is mapped to the correct input variable from the previous block.