Test SendGrid Inbound Parse Fields With a Local Codex Fixture
Validate which message fields a SendGrid parsed-mode handler should recognize in a local test before connecting a mailbox or webhook.
中文Setup for Codex
Use Codex with local file access and a synthetic parsed-mode record. The fixture represents decoded form fields, while hosted Inbound Parse requires an authorized receiving domain and endpoint.
- Open the pinned Twilio AI repository revision and copy this skill directory, with its companion files, into your Codex project's .agents/skills directory.
- Open Codex in a scratch project and select the matching Twilio SendGrid skill. Use the local test fixture before configuring credentials for any live API check.
Example task
Ask Codex to parse this local decoded form record and report sender, subject and text. Do not connect a mailbox or start a server.
{"from":"Reader <reader@example.com>","subject":"Book club question","text":"Which room is booked?"}Expected result
The report shows reader@example.com, Book club question and Which room is booked? It identifies missing optional HTML and attachments without opening files or rendering message content.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
How do SendGrid Inbound Parse parsed and raw modes differ?
Parsed mode provides separate fields such as sender, subject and message text. Raw mode puts the original email content into a message field for MIME parsing.