Read-only Inbox
Give your teammate a read-only inbox so it can fetch emails during a run — 2FA codes, verification emails, password resets.
How it works
- Enable the inbox on a teammate. They get a unique email address
- Emails sent to that address are stored without triggering any run
- During a run, the agent reads emails using three built-in tools
Inbox vs Email Inbox: The email inbox triggers a run when an email arrives. The read-only inbox is for retrieval mid-run. Use both together: email inbox for incoming tasks, read-only inbox for verification flows.
Enable
Agent Tools
When fetchmail is enabled, three tools are automatically available to the agent during runs:
Example: 2FA Code Retrieval
The agent can wait for a verification email to arrive:
Agent: I'll sign up and wait for the verification code...
→ calls wait_for_email(from_email="noreply@service.com", subject_contains="verification", timeout_seconds=60)
→ receives: {"id": 42, "subject": "Your verification code", "body": "Your code is 847291", ...}
Agent: Got the code: 847291. Entering it now.
Storage Limits
- 100 emails per teammate — oldest are automatically deleted when the limit is reached
- 48-hour TTL — emails older than 48 hours are cleaned up daily
- Emails are scoped to the teammate and isolated per
user_idwhen set
Disable
Python
Disabling stops new emails from being stored. Existing emails remain until cleaned up.
What's Next
- Email Inbox — trigger runs from inbound emails
- Tools — configure what tools your teammate can use
- Users — isolate data per end-user with
user_id