Classify SendGrid Unsubscribe and Bounce Suppressions in Codex
Review suppression records from an authorized export and distinguish global unsubscribes, category preferences and bounces before deciding what to investigate.
中文Setup for Codex
Use a disposable local fixture. Account diagnostics require an approved SendGrid connection with read access, and this example only classifies records.
- 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
Make a table with alpha@example.com marked global unsubscribe, beta@example.com marked Product Updates group unsubscribe, and gamma@example.com marked hard bounce. Ask Codex for one row describing the scope and reason for each, keeping every suppression intact.Expected result
The output classifies Alpha as globally unsubscribed, Beta as opted out of Product Updates, and Gamma as blocked by a hard bounce. It makes no changes to suppression state.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Is a SendGrid category unsubscribe the same as a global unsubscribe?
A category unsubscribe applies to its designated suppression group. A global unsubscribe has wider scope. Keep these states separate when reviewing an export.