Anyone know why the Zendesk ticket creation data action returns a 400 Bad Request with ‘invalid email format’?
The email field is populated correctly from the interaction context in Architect, just like the simple text fields work in Zendesk macros.
We are using the default Zendesk integration endpoint without custom headers.
check the email field in architect for hidden whitespace or null values. the zendesk api rejects empty strings or malformed inputs from data actions, so add a regex validation step before the call.
If I remember correctly, Zendesk rejects emails with non-ASCII characters or trailing spaces, which often slips through Architect context mappings.