twilio-sendgrid-inbound-parse

Point your domain or subdomain MX records to mx.sendgrid.net, then add a host and webhook URL under SendGrid Console Settings > Inbound Parse. SendGrid POSTs parsed fields like from, subject, text, html, and attachments to your endpoint as form data.

Read the attachments field for the count, then retrieve each file from request.files using keys attachment1, attachment2, and so on. The attachment-info field contains JSON metadata for each file.

Parsed mode extracts fields like from, subject, text, and html into form data automatically. Raw mode posts the entire MIME message as rawEmail, which you parse yourself when you need full headers, DKIM signatures, or non-standard MIME parts.

No, MX records must point to mx.sendgrid.net, which would disrupt existing email on that domain. Use a subdomain such as inbound.yourdomain.com so services like Google Workspace or Microsoft 365 keep working on the primary domain.

Messages over 30MB are rejected, all mail for the configured domain goes to a single webhook URL with no pre-filtering, and delivery order is not guaranteed. Implement filtering, rate limiting, and payload validation in your own handler.

Enable signed Inbound Parse webhooks, which use ECDSA signature verification like SendGrid Event Webhooks. This is recommended over IP allowlisting because SendGrid webhook traffic comes from dynamic cloud infrastructure with frequently changing IPs.