Guides
Task-based guides for operating and extending Email SDK.
Use these guides when you are operating a production send path or building something that should live outside one send call: fallback routes, tests, reusable plugins, custom provider adapters, or community packages.
If you want to support a provider that Email SDK does not officially maintain, start with Publish a community adapter. Community adapters live in their own npm packages and can be listed in the docs without becoming official.
Operate
Production send pipeline
Combine adapters, validation, retries, fallback routes, observability, tests, and CLI checks.
Test email behavior
Use memory providers and capture plugins to assert send behavior.
Build
Create your first plugin
Build a policy plugin that blocks sends missing required metadata.
Create an adapter
Implement a provider adapter and expose it as a plugin.
Publish a community adapter
Publish a third-party provider package and list it without making it official.
Where reference lives
Guides are procedural. Use the reference pages when you need exact fields and contracts:
| Need | Page |
|---|---|
| Client options | Client |
| Message shape | Message |
| Adapter contract | Adapter contract |
| Plugin types and lifecycle | Plugin API |
| Provider field limits | Field support |