🔖 Feature description
Add a built-in Email Sandbox provider that can be used during local development, testing, and staging instead of a real email provider. (or add delivery rules for development environment)
The sandbox would capture outgoing emails and provide a dedicated UI to inspect, preview, search, and manage messages without sending them to real recipients and reviewing actual email content, which was sended out. This would allow developers to validate notification workflows in a safe environment while keeping the production configuration unchanged.
Alternative would be to save emails to review them.
🎤 Why is this feature needed ?
Developers typically need different email behavior depending on the environment. While production requires reliable email delivery, development benefits from a safe sandbox that prevents accidental emails from reaching real users, also real scenarios like mass sending could be tested safely.
Today, many teams rely on external tools such as Mailtrap for this purpose. Having this functionality built directly into Novu would simplify setup, improve onboarding, and provide a better out-of-the-box developer experience.
It could also be a paid feature for novu cloud to opt in or usage based 😇
Benefits include:
Prevent accidental email delivery during development.
Reduce external tooling and configuration.
Simplify onboarding for new developers.
Test complete notification workflows without affecting real users.
Keep production email configuration separate from development.
✌️ How do you aim to achieve this?
Implement a native Email Sandbox provider that behaves like any other email provider but captures emails internally instead of delivering them and include them into activity feed or as a seperate section in the dashboard.
Also add ability to manage forwarding rules.
f.ex. to all developers.
Potential features include:
Inbox for captured emails.
HTML and plain-text previews.
Attachment preview and download.
Search and filtering by recipient, subject, channel, or date.
Email metadata (headers, recipients, timestamps).
Environment separation (local, development, staging).
Automatic forwarding of captured emails to configurable email addresses for QA or stakeholders.
Allowlist of recipients that are permitted to receive real emails while all others remain sandboxed.
Recipient override (e.g. route every outgoing email to a single test address).
Email release/replay to resend captured messages.
Webhooks or API access for automated integration tests.
Shareable preview links for designers, QA, and product teams.
Easy switching between the sandbox and production providers.
🔄️ Additional Information
https://github.com/mailtrap/mailtrap-docs/blob/main/documentation/getting-started/email-sandbox.md
👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
Maybe 😇
🔖 Feature description
Add a built-in Email Sandbox provider that can be used during local development, testing, and staging instead of a real email provider. (or add delivery rules for development environment)
The sandbox would capture outgoing emails and provide a dedicated UI to inspect, preview, search, and manage messages without sending them to real recipients and reviewing actual email content, which was sended out. This would allow developers to validate notification workflows in a safe environment while keeping the production configuration unchanged.
Alternative would be to save emails to review them.
🎤 Why is this feature needed ?
Developers typically need different email behavior depending on the environment. While production requires reliable email delivery, development benefits from a safe sandbox that prevents accidental emails from reaching real users, also real scenarios like mass sending could be tested safely.
Today, many teams rely on external tools such as Mailtrap for this purpose. Having this functionality built directly into Novu would simplify setup, improve onboarding, and provide a better out-of-the-box developer experience.
It could also be a paid feature for novu cloud to opt in or usage based 😇
Benefits include:
Prevent accidental email delivery during development.
Reduce external tooling and configuration.
Simplify onboarding for new developers.
Test complete notification workflows without affecting real users.
Keep production email configuration separate from development.
✌️ How do you aim to achieve this?
Implement a native Email Sandbox provider that behaves like any other email provider but captures emails internally instead of delivering them and include them into activity feed or as a seperate section in the dashboard.
Also add ability to manage forwarding rules.
f.ex. to all developers.
Potential features include:
Inbox for captured emails.
HTML and plain-text previews.
Attachment preview and download.
Search and filtering by recipient, subject, channel, or date.
Email metadata (headers, recipients, timestamps).
Environment separation (local, development, staging).
Automatic forwarding of captured emails to configurable email addresses for QA or stakeholders.
Allowlist of recipients that are permitted to receive real emails while all others remain sandboxed.
Recipient override (e.g. route every outgoing email to a single test address).
Email release/replay to resend captured messages.
Webhooks or API access for automated integration tests.
Shareable preview links for designers, QA, and product teams.
Easy switching between the sandbox and production providers.
🔄️ Additional Information
https://github.com/mailtrap/mailtrap-docs/blob/main/documentation/getting-started/email-sandbox.md
👀 Have you spent some time to check if this feature request has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
Maybe 😇