SendGrid

SendGrid is the transactional email platform most engineering teams reach for when in-app notifications aren't enough — order confirmations, password resets, billing alerts, the email that has to actually arrive. When the integration lands, myai will treat SendGrid as a fan-out target for any function that needs to send mail at scale, with the same template, suppression, and analytics surface SendGrid exposes natively.

What you'll be able to do

• Send transactional email from automations — a workflow ends, an email goes out. Order confirmation, status update, password reset.
• Template-based sends — SendGrid templates work natively; functions pass dynamic data, SendGrid composes.
• Suppression management — automations can read suppression state (bounced, unsubscribed, spam-reported) before sending to avoid further damage.
• Engagement analytics — open rates, click rates, bounce data queryable for the workflows that need to know "did the email actually land."
• Inbound parse — for the two-way workflows where a customer reply needs to trigger downstream action.

How it'll work

SendGrid API key. Generate one at Settings → API Keys in your SendGrid account; the integration stores it and any function in the workspace can use it for sends.

Tell us you want SendGrid

Use cases we're hearing

• Transactional notification fan-out — workflows end, the right customers get the right email automatically.
• Engagement-driven workflows — a function reads click data and routes high-engagement contacts to a different downstream sequence.
• Bounce/suppression maintenance — daily function reads suppression state, syncs into CRM so reps stop trying to reach bad addresses.

Reference

• Connection model: SendGrid API key (Bearer token)
• Scope: ~45 operations across send, templates, suppressions, analytics, inbound parse
• Also reachable through the Twilio integration when both products are on the same account