Your password-reset flow needs an inbox to test against. Your invitation flow too. Your email-verification gate too. The classic setup is a " test+pr-1234@yourdomain.com " alias on a shared mailbox, polling Gmail's API, hoping nothing else lands while the test runs. It is fragile, it leaks state across PRs, and your credentials live in CI. A managed agent account flips this. Each PR gets a fresh inbox, lives only for the duration of the test run, and tears itself down at the end. What this gives you One inbox per PR, isolated from every other test Real send/receive — not a mock No shared Gmail credentials in CI Cleanup is one command per inbox Parallel test workers do not collide The full GitHub Action # .github/workflows/e2e.yml name : E2E with ephemeral inbox on : pull_request : branches : [ main ] jobs : e2e : runs-on : ubuntu-latest steps : - uses : actions/checkout@v4 - name : Install Nylas CLI run : curl -fsSL https://cli.nylas.com/install.sh | bash env : NYLAS_INSTALL_DIR : ${{ github.workspace…