twilio-sendgrid-inbound-parse
Receive inbound email via SendGrid Inbound Parse webhook. Covers MX record setup, parsed vs raw mode, handling attachments, and common pitfalls. Use when building email-to-app workflows like support ticket creation or email processing pipelines. Requires a SendGrid API key (SG.-prefix) — not applicable to the Twilio Email API (comms.twilio.com).
Install
With your agent
Install OMGSkills skill "twilio/ai:skills/sendgrid/twilio-sendgrid-inbound-parse" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/twilio/ai /tmp/ai && ln -s /tmp/ai/skills/sendgrid/twilio-sendgrid-inbound-parse ~/.claude/skills/twilio-sendgrid-inbound-parseFrom README
Overview Inbound Parse converts incoming email into HTTP POST requests to your webhook endpoint. SendGrid receives the email at your domain's MX records and forwards the parsed content to your application. --- Configure MX records: Point your domain (or subdomain) to mx.sendgrid.net Add webhook: SendGrid Console > Settings > Inbound Parse > Add Host & URL Choose mode: Parsed (default) or Raw Subdomain recommended: Use inbound.yourdomain.com to avoid disrupting existing email on yourdomain.com. --- Parsed Mode (Default) SendGrid extracts fields and POSTs them as form data: | Field | Description | |-------|-------------| | from | Sender address ("Name ") | | to | Envelope recipient | | subject | Email subject line | | text | Plain text body | | html | HTML body | | envelope | JSON string with to array and from | | attachments | Number of attachments (as string) | | attachment-info | JSON metadata for each attachment | | attachment1, attachment2...