The inbox feature is powered by a direct integration with our email backend. When a test step requires checking email (e.g., “Wait for the welcome email”), the agent queries the inbox system directly.
Polling: The agent polls for new emails for up to 3 minutes. If no matching email is found within this time, the step fails.
No Pagination: The system always looks for the newest email that matches your criteria. It does not support pagination or “get more” requests.
Text-Only View: The agent sees a text summary of the email (subject, match reason, attachment summary), not the raw HTML or JSON.
The inbox feature only works with emails managed by the QA.tech system.
Config Type
Behavior
Inbox Access
Single Use
Generates a unique email for each test run. Best for isolation.
✅ Yes
Fixed / Project
Uses a stable email address. Good for whitelisting.
✅ Yes
Email + Password
Generates a unique email once per config.
✅ Yes
External Email
Using your own Gmail/Outlook address in a test step.
❌ No
External emails are not supported. The agent cannot access personal
inboxes like Gmail or Outlook. You must use a system-generated email config
for the agent to read emails.
Shared Inboxes: If multiple tests use the same email inbox simultaneously (e.g., two password reset tests), emails may get mixed up. Use separate email configs for concurrent tests.
Sharing Emails Between Tests: If Test B needs to check an email triggered by Test A:
Output Values: In Test A, save the email address as an Output Value. In Test B, use that value to tell the agent which inbox to check.
Shared Configs: If using a Fixed/Project email, both tests can use the same config. Be mindful of the time window (Test B must start before the email arrives, or you must trigger the email during Test B).
Cross-Test Limitations: Because of the strict time window, a test cannot see emails that arrived before it started.
If Test A triggers an email and finishes, and then Test B starts and tries to read that email, Test B will fail to find it.
Solution: Combine the trigger and verification into the same test, or ensure the email is triggered after the verification test starts (e.g., using dependencies where the second test triggers the resend).
Timeout: The agent will wait up to 3 minutes for expected emails before failing.
Extending the wait: You can add explicit “Wait” steps (e.g., “Wait 2 minutes”) before the email check. Since the inbox cursor is fixed at the start of the test run, waiting before checking effectively extends the window for receiving emails.
Invitation Links Since the browser state will be kept when opening the email you should log out after inviting a user to avoid that the invitation link redirects to the inviters account.