The value is not a shorter send call; it is a tested account lifecycle, normalized mailbox model, change stream, and recovery path that several product teams can share.
One connected mailbox can support a CRM timeline, support inbox, recruiting workflow, and agent review queue when permissions and ownership are explicit. Teams stop rebuilding OAuth and sync for each feature.
A unified contract can cover Gmail, Outlook, and other IMAP mailboxes while provider extensions preserve capabilities that do not fit the common denominator.
Token refresh, stale cursors, watch renewal, duplicate notifications, backoff, and reconnect prompts are infrastructure concerns. Solving them once reduces inconsistent behavior across product surfaces.
A unified layer adds vendor or platform dependency, a data-processing boundary, and possible latency. Evaluate provider coverage, export paths, incident behavior, security evidence, and native-field access before adopting it.
Only if its supported providers and lifecycle behavior match the product. A thin wrapper that lacks recovery, native fields, or real-account tests can create more work later.
Ask for provider-by-provider operation coverage, real-account conformance results, security controls, sync and reconnect behavior, data deletion evidence, and clear capability status.
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.