Email Inbox

The Email Inbox connector reads and searches email activity that already flows through the platform. Inbound mail arrives through the platform’s inbound email webhook and outbound mail goes out through the platform’s email rail; both are persisted to your tenant’s contact timeline, and this connector reads that timeline directly. There is no external mailbox polling — no IMAP, no Gmail or Microsoft 365 API — and no credentials to store.

Setup

There is nothing to set up. Email Inbox is listed under Settings → Connectors with its + button disabled, and POST /api/v1/connectors/email_inbox/connect returns 400 because the connector uses the platform contact timeline rather than external credentials. It does not occupy an integration slot and has no permission policy row, because no connector instance is ever created for it.

To get email into the timeline, provision an email identity for an agent (see Resend). Replies to that address arrive through the inbound webhook and become part of the contact’s timeline, which the CRO and CFO already consult before every outbound touch through the Contact Timeline service.

Connector tools

All tools are read-only database queries scoped to your tenant.

Tool	What it does
get_inbox_summary	Recent threads and flagged items; unread count is always 0 because read state is not tracked
get_threads	List email threads with filtering and pagination
get_thread_messages	All messages in a specific thread
search_emails	Search emails by query string
get_contacts	Contacts extracted from email correspondence
get_labels	Labels derived from message direction (inbound / outbound)

Disconnect

Not applicable — there is no stored credential and no instance to remove.