What teams use Inflovy test inboxes for.
Receive-only inboxes for the emails your product sends while it is under test. Pick the workflow closest to yours; each guide shows the setup, the pitfalls of the personal-inbox approach and the code where it applies.
- How-toRead the guide
Playwright email testing: wait for the verification email
How to test signup and OTP flows in Playwright: create a test inbox, sign up with it, wait for the verification email, and read the extracted code. Under 15 lines.
- How-toRead the guide
Cypress OTP email testing without a polling loop
Test signup, OTP and magic-link emails in Cypress: create a test inbox with cy.request, sign up with it, wait for the verification email, and type the extracted code.
- Use caseRead the guide
Disposable email for testing that is private and keeps the code
A disposable email address for testing signups, with the verification code shown as it arrives. Private, receive-only, one click, no account. Keep it and share it with your team when you want.
- Use caseRead the guide
A shared inbox for test accounts the whole team can read
A shared test inbox so QA, engineering and product can all see the verification emails for every test account, without a shared password or forwarding.
- Use caseRead the guide
Verification email testing your whole team can see
A team inbox for verification emails: account confirmations, password resets and magic links land where every teammate can open them, with the link and code extracted.
- Use caseRead the guide
Shared OTP email for teams
A shared OTP email inbox: one-time codes for test and team accounts land in a workspace inbox where any member can copy them, instead of one person’s phone or Gmail.
- Use caseRead the guide
A test inbox per staging environment
One test inbox per environment: staging, UAT and dev signups each get their own receive-only inbox inside a project, visible to the team and searchable.
- Use caseRead the guide
A test email inbox built for QA teams
A test email inbox for QA teams: private inboxes per test account, the verification code shown on arrival, history the whole team can search, and an API for automated suites.
- Use caseRead the guide
A team-owned inbox for vendor and tool accounts
Register SaaS tools and vendor accounts to a workspace-owned inbox so login codes and notices reach the team, not the employee who signed up two years ago.