/Integrations
v1.2SendGrid
Validate fallback transactional delivery and sender configuration.
Integration
SendGrid
Confirms transactional email fallback and event webhook readiness.
SendGrid failures at launch often split between sender identity—single sender vs authenticated domain—and webhooks that never receive bounce or delivery events. PreFlight validates API key scope, checks sender readiness before delivery tests, and confirms webhook endpoint details for event callbacks.
Requirements
- SendGrid API key with Mail Send permissions
- Verified sender identity or authenticated sending domain
- Event webhook endpoint URL for delivery and bounce callbacks
Prefer domain authentication
Use domain authentication for production, not only a single sender identity, when launch email volume or deliverability matters.
What PreFlight checks
| Probe | What it proves |
|---|---|
| API key scope | The key is valid and has permissions for mail send checks. |
| Sender readiness | Sender identity or domain authentication is complete before delivery tests. |
| Delivery test | A safe transactional send can be attempted when configured. |
| Webhook readiness | Event webhook endpoint details are available for Phase 2 callback checks. |
Failure guidance
| Symptom | Fix |
|---|---|
| Invalid API key | Create a restricted key in SendGrid → Settings → API Keys. |
| Sender not verified | Complete single sender verification or full domain authentication. |
| Webhook unreachable | Deploy the event webhook route and confirm it accepts POST from SendGrid. |
| Deliverability issues | Authenticate the sending domain and warm up IP/domain before high-volume launch mail. |
Dashboard setup
- Navigate to Integrations → SendGrid in your PreFlight project.
- Paste the API key and verified sender or authenticated domain details.
- Add your event webhook endpoint URL for delivery and bounce events.
- Run Pre-Flight Check and resolve sender or webhook warnings.