Hi @Product ,
I've got a WA configured with a connected account that gets an unauthorized request response when I use the WA, but not when I use the HTTP request WA and include the bearer token.
Is the bearer token included in the header when using this WA?
Customer.io WA Result
Execution ID: 3c30d0119b3d02fa6b31ae4a96587e16
Response body: {
"meta": {
"error": "Unauthorized request"
}
}
Response code: 401
Response headeres: {
"Access-Control-Allow-Origin": "*",
"Cache-Control": "no-cache, no-store, must-revalidate, max-age=0",
"Content-Length": 56,
"Content-Type": "application/json; charset=utf-8",
"Date": "Fri, 23 Jan 2026 20:28:49 GMT",
"Status": "401 Unauthorized",
"Via": "1.1 google",
"Alt-Svc": "h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000"
}
HTTP Request Result
Body: {
"meta": {
"error": "\"from\" address domain axolongevity.com has not been verified. Verify your domain (https://customer.io/docs/authentication) to use this \"from\" address."
}
}
Response: 400 (Expected because of missing from value)
Headers: {
"Access-Control-Allow-Origin": "*",
"Cache-Control": "no-cache, no-store, must-revalidate, max-age=0",
"Content-Length": 190,
"Content-Type": "application/json; charset=utf-8",
"Date": "Fri, 23 Jan 2026 20:35:45 GMT",
"Status": "400 Bad Request",
"Via": "1.1 google",
"Alt-Svc": "h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000"
},
body with added from value:
Execution ID:
b80c011d-b039-4e9e-8ff2-3e610608838d
{
"meta": {
"error": "\"from\" address domain axolongevity.com has not been verified. Verify your domain (https://customer.io/docs/authentication) to use this \"from\" address."
}
}
