SendGrid API integration for AI agents
Sendgrid for mailing, you can create campaigns send them edit templates and explore statistics via Escalator.
Connect SendGrid API to Chase Agents as an API connection, then use it in plain-English automations — on the web, in Slack, or inside ChatGPT and Claude via MCP. Chase Agents builds the workflow and deterministic code runs it.
How to connect SendGrid API
Add SendGrid API from the Chase Agents connections marketplace as API connection, provide the required credentials, and reference it in your automation steps. See plans or read the connection guide.
About SendGrid API
When programmatically sending HTML emails through SendGrid, particularly when transitioning between its transactional API and the Marketing Campaigns API, we encountered a common yet tricky formatting challenge. Emails that looked perfect when sent transactionally using a dynamic template ID (d-xxxx) suddenly appeared unformatted, with literal newline characters (\n) sprinkled throughout, when the same HTML content was used for a Marketing Campaign Single Send via its API.
The Core Issue & What We Learned:
The discrepancy arises from how SendGrid's different systems process HTML. The transactional email engine, when given a template ID and dynamic data, robustly handles HTML structure and CSS within <style> blocks. However, when providing raw HTML directly to the Marketing Campaigns API's html_content field (even if that HTML is sourced from a perfectly good template), the processing is different. The Marketing Campaign system can misinterpret JSON-escaped newline characters (which are necessary if your source HTML string has readable newlines) as literal text to be displayed, rather than simple whitespace. Furthermore, CSS in <style> blocks may not be as reliably applied across all email clients through this pathway without additional processing that SendGrid's own Marketing Design tools might perform.
The Fix That Worked for Us (and a Best Practice):
The key to resolving the immediate issue of unwanted newline characters appearing in the campaign email was to minify the HTML content before sending it to the API. This means removing all actual newline characters from the HTML string, making it a single, continuous line of code. When this single-line HTML string (still properly JSON-escaped for the API call itself) was provided in the html_content field of the POST /v3/marketing/singlesends request, the email rendered correctly without the extraneous \n characters.
While minifying fixed the newline problem, for truly robust cross-client email formatting, inlining all CSS styles directly onto HTML elements is the gold standard. Although our minified HTML (which still contained a <style> block) worked in this instance, relying on CSS inlining would provide even greater assurance. Alternatively, for complex marketing emails, leveraging SendGrid's own Design Editor within the Marketing Campaigns UI to build or import designs allows their system to optimize the HTML and CSS specifically for campaign delivery.
In summary, when driving SendGrid Marketing Campaigns via API with your own HTML, ensure your html_content is a clean, single-line string, and for best results, consider CSS inlining or using SendGrid's dedicated design tools.