Contract-Test API Emails in GitHub Actions

Short summary

A guide to contract-testing API-triggered emails in GitHub Actions by creating run-scoped inbox IDs that correlate each test to a specific workflow run. The approach avoids brittle end-to-end UI tests by asserting at the API boundary: verifying exactly one matching message, correct payload context, and fast triage via a shared run ID. Includes concrete YAML and JavaScript examples for implementation.

• •Use run-scoped inbox IDs to isolate email tests per CI job
• •Assert at the API boundary instead of bolting email checks onto UI suites
• •Fail fast with narrow assertions on message count, recipient, and key content

Generated with AI, which can make mistakes.