Hey everyone, running into a weird issue with our outbound email campaign setup. We are using a custom connector to push leads from our internal CRM into a Genesys Cloud campaign. The goal is to send personalized HTML emails that include our standard corporate signature.
The problem is that when I use the POST /api/v2/outbound/campaigns endpoint to update the campaign configuration, specifically the emailTemplate section, the API returns a 400 Bad Request error. The error message is pretty vague: Invalid template content detected. Sanitization failed.
I’ve stripped down the HTML to the bare minimum, just a <div> with some text and a <p> for the signature. Even then, it fails. If I remove the signature block entirely, the campaign saves fine. I know Genesys has strict rules about signature stripping in inbound, but this is outbound.
Here is a snippet of the payload causing issues:
{
"emailTemplate": {
"content": "<html><body><p>Hi {{lead.firstName}},</p><p>Check this out.</p><p>Best, <br>John Doe <br>Marketing Team</p></body></html>"
}
}
I’m using the Genesys Cloud SDK for Python (version 140.0.0) to make these calls. I also tried using the REST API directly via Postman, same result. I suspect there might be an issue with how the campaign engine parses HTML entities or perhaps a hidden character in the signature block that triggers the sanitizer.
Has anyone else hit this wall with outbound email templates? Are there specific tags or entities that are blacklisted in the campaign builder that aren’t documented? Any help would be appreciated.