Connect Gmail
Allowed account: usechainable@gmail.com. Sign-in requests sending access; read-only inbox access is requested separately when enabled.
Continue with GoogleCompose
Queue
No messages in the queue.
Application inbox
Reconnect Google and grant Mailer read-only Gmail access before syncing. Your existing send connection remains available.
Enable inbox accessGoogle's gmail.modify consent is broader than archiving: it grants read, compose, and send capability. Mailer separately checks the exact granted scopes and uses this feature only for a manually confirmed archive of a reviewed thread; agent tokens still cannot send or read inbox contents.
Read-only sync · latest 50 inbox threads from the last 90 days · no attachment downloads. Suggestions are rule-based and always require your review. Sync itself never changes Gmail; the only optional mutation is a separately authorized, owner-confirmed archive of a reviewed thread. No deletes, forwards, or automated sends.
No cached inbox threads. Connect inbox access, then sync.
History
| Subject | Recipient | Status | Updated |
|---|
No messages yet.
Activity log
Controls
Greenhouse verification-code handoff
Configured sender and authentication domain have not been loaded.
This separate permission allows OEJ to retrieve one current, authenticated message addressed to the fixed owner account and hand its code to the same paused browser session after you explicitly arm and fill it. It cannot send mail, read or sync the general inbox, or submit an employer form. Disable it here at any time.
Agents
Use it as a Bearer token with the agent API. It is shown once.
No agent tokens.
Agent API
Agent tokens are draft-only. They cannot read inbox messages or send mail; review and send drafts yourself in Mailer.
Authorization: Bearer <token>
Content-Type: application/json
{"to":"person@example.com","subject":"Subject","body":"Message"}