Gmail sending requires a valid user grant, an RFC-compliant MIME message encoded for the API, an authorized sender identity, and application-level idempotency.
The gmail.send scope can authorize sending without general mailbox reading. Draft management, replies using stored context, or mailbox synchronization may require additional scopes and a different Google verification burden.
Build valid From, recipients, subject, body alternatives, and attachment parts, then base64url-encode the complete raw message. Use the connected account or a Gmail-configured alias as the sender.
For a reply, include the appropriate Gmail thread ID and standards-based reply headers. Matching subject alone is insufficient; validate the parent message and participants before constructing reply-all recipients.
Persist an application idempotency key and final content hash before the provider call. Store Gmail's returned message ID, reconcile the Sent label if needed, and distinguish provider acceptance from delivery or engagement.
No. The send operation expects a base64url-encoded raw Internet message, normally constructed as MIME by a mail library.
No. Send-only access does not grant general mailbox reads. Request broader access only if the product genuinely needs it and can meet the added requirements.
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.