A complete Gmail connector joins OAuth, MIME messages, labels, threads, history-based sync, Pub/Sub watches, and recovery into one account lifecycle.
Sending alone can use gmail.send, while mailbox reads, drafts, and label changes need different access. Document the reason for each requested scope and complete the applicable Google verification before production onboarding.
Normalize common fields without discarding threadId, historyId, label IDs, or raw MIME structure. Gmail labels are not identical to hierarchical folders, and a message can carry several labels at once.
Create the baseline first, then consume history records after a Pub/Sub wake-up. Renew watches before expiration and keep a periodic reconciliation path because notifications can be delayed or dropped.
A history cursor outside Gmail's available range returns HTTP 404 and requires a fresh full sync. Token revocation, quota responses, MIME parse errors, and missing messages should each produce a distinct, actionable account or item state.
No. Labels can overlap on one message, while many folder models imply a single location. A unified schema should retain the Gmail label set instead of forcing a lossy conversion.
No. Pub/Sub tells the service that mailbox history advanced; history.list and resource retrieval provide the actual changes.
Not yet. Gmail, Microsoft Graph, and IMAP/SMTP connectors are planned. This guide documents the intended architecture and the provider requirements a production release must satisfy.
DewEngine is in development. Real use cases decide what ships first.