One inbox per scenario
Keep test messages isolated by creating a fresh temporary address for the flow under test.
Email testing workflow
Test email flows with temporary inboxes.
Create a temporary mailbox for each scenario, trigger the product action that sends mail, wait for the incoming message, read it through the API or CLI, and let your test code extract the product-specific link or code.
API and CLI friendly
Use API keys or mailfab CLI JSON output to create, wait, read, and delete test inboxes.
Webhook-aware automation
Signed-in workflows can use webhook notifications for new inbound mail when polling is not the best fit.
Test shape
Keep parsing logic in your own test suite.
Mailfab provides the temporary inbox, polling, message reading, and cleanup primitives. Your application test remains responsible for finding the expected link, code, sender, or subject in the message content.
- Create a mailbox before the browser action.
- Trigger the signup, invite, password reset, or magic link email.
- Read the message and assert the product-specific result in your test runner.
Manual to automated
Start with guest inboxes, move to authenticated automation.
The guest inbox is useful for quick manual checks. When temporary email becomes part of CI, Playwright, or agent workflows, signed-in mailboxes add API keys, CLI usage, webhooks, and share links.
- Use guest inboxes for quick receive-only checks.
- Use signed-in mailboxes when the test needs API access or a stable mailbox record.
- Use webhooks when your workflow should react to inbound mail.