SendGrid

**Verdict:** A mature, well-documented SendGrid integration suitable for most transactional and marketing email workflows if you already use (or can use) the Maton gateway. **Strengths:** - Broad coverage of SendGrid v3 features: mail send, marketing contacts/lists/segments, templates, senders, suppressions, stats, and API keys. - Managed OAuth through Maton simplifies credential handling; you only manage a Maton API key. - Documentation is unusually complete: concrete endpoint paths, example payloads, pagination details, async job handling, and troubleshooting steps. - Supports multi-account scenarios via `Maton-Connection` header. **Key Risks / Limitations:** - Hard dependency on Maton (gateway.maton.ai and ctrl.maton.ai): if Maton is unavailable, all operations fail even if SendGrid is up. - Requires prior setup of a Maton account, MATON_API_KEY, and OAuth connection, which may be a barrier in some environments. - Powerful, potentially destructive operations are exposed (e.g., deleting contacts, lists, API keys, and suppressions); incorrect use can damage a production email setup. - No built-in guardrails on email content or recipient policies, so misuse could lead to spam complaints or policy violations if higher-level logic is not careful. **Recommended Scenarios:** - You need to programmatically send transactional or marketing emails and already have (or are willing to set up) Maton + SendGrid. - You want a single, consistent HTTP integration to manage SendGrid contacts, lists, and templates without juggling API keys yourself. - You need to inspect and manage deliverability issues (bounces, blocks, spam reports) or gather stats for reporting across campaigns. **Use with extra care when:** - Operating in production on a shared or critical SendGrid account—validate all delete/update operations and consider read-only flows where possible. - Handling sensitive or regulated content—enforce your own compliance checks before calling mail send endpoints.