2.5k
GitHub Stars
3
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill sendgrid-skills- _meta.json997 B
- README.md4.0 KB
- SKILL.md2.2 KB
Overview
This skill lets you receive and parse inbound email using SendGrid Inbound Parse Webhook. It guides MX record setup, webhook configuration, multipart/form-data payload parsing, attachment handling, and security hardening. Use it to convert incoming email into structured data for apps, support systems, or automated workflows.
How this skill works
Create an MX record pointing a subdomain to mx.sendgrid.net and configure the Inbound Parse destination URL in SendGrid. SendGrid POSTs the parsed message as multipart/form-data containing fields like from, to, subject, text, html, headers, envelope, attachments, and file parts. The skill parses those parts, extracts bodies and attachments, and suggests endpoint protections such as basic auth, IP allowlists, request size limits, and content validation.
When to use it
- Programmatically ingest incoming emails into an app or database
- Build email-to-ticket or email-to-task workflows
- Handle email replies for conversational bots or support systems
- Process attachments uploaded via email
- Implement inbound email parsing where SendGrid is your MX provider
Best practices
- Use a dedicated subdomain for MX records to avoid disrupting existing email services
- Require basic authentication and HTTPS on the webhook endpoint
- Allowlist SendGrid IP ranges and enforce request size limits (10–25 MB recommended)
- Validate multipart/form-data content-type and parse attachments with a robust library
- Sanitize HTML before rendering and run attachment virus scanning
Example use cases
- Support system: convert incoming support emails into tickets with parsed subject, body, and attachments
- Email-to-app: extract structured data from incoming emails and push to a database or webhook
- Auto-responder: trigger templated replies or workflows when specific subjects or senders arrive
- Attachment processor: accept image/PDF uploads by email and run OCR or file processing
- Conversational bot: accept user replies by email and inject them into a messaging flow
FAQ
No. Inbound Parse does not provide an official signature. Treat payloads as untrusted and secure the endpoint with auth, IP allowlists, and size limits.
How do I test payload parsing locally?
Capture a sample multipart/form-data payload from SendGrid and run it through your multipart parser or a local debug script. Ensure your endpoint returns 200 OK to let SendGrid mark delivery as successful.