Convex

@opencoredev/convex-email is a real Convex Component: it owns isolated tables, queues provider work outside your mutation, retries safe failures, deduplicates sends, stores an event timeline, and exposes reactive delivery status.

Email SDK owns message validation and provider adapters. The Convex component owns durable application state around those sends.

What you get

Fast mutations. send stores the message and returns an email id before the provider request runs.
Durable idempotency. Reusing an idempotency key returns the original email id instead of queueing another message.
Retry and recovery. Failed attempts use exponential backoff, stale processing work is recovered safely, and terminal failures can be retried manually.
Provider portability. Use any serializable built-in Email SDK adapter configuration, including named fallback routes.
Reactive status. Query queue state, provider receipts, attempted adapters, normalized delivery state, and the complete event timeline.
Safe testing. Redirect all recipients to a sandbox mailbox or use the in-memory adapter without changing application flow.

Public API

Method	Purpose
`send(ctx, message)`	Queue one email and return its component id.
`sendBatch(ctx, messages)`	Queue up to 100 messages and return ids in input order.
`status(ctx, { emailId })`	Read the current stored email state.
`listEvents(ctx, { emailId })`	Read the ordered queue, attempt, retry, and webhook timeline.
`cancel(ctx, { emailId })`	Cancel work that has not started.
`retry(ctx, { emailId })`	Start a fresh retry cycle for a terminal failure.
`setConfig(ctx, config)`	Replace test, sender, retry, and retention defaults.

Install and configure

Mount the component, map provider secrets, and create the server client.

Send and track email

Queue messages and expose reactive status to your application.

Process webhooks

Verify provider events and store normalized delivery state.

Test and recover

Redirect recipients, inspect failures, cancel work, and retry safely.