Sanctum Notify / Operational email
A form submitted. A task updated. A report ready. Turn the events in your business into useful emails, with a shared service for email preparation and dispatch.
Built for the Digital Sanctum stack. Available for guided integration.
Check permissions · Render template · Dispatch
The relevant details, in a consistent format, with a clear next step.
Accepted by the email providerAn example, not a live send. Provider acceptance is not proof of inbox delivery or that someone has read the message.
Less scattered sending logic
Instead of building email templates, provider connections and retry handling into every application, use a shared notification service. Sanctum Notify accepts authenticated requests, prepares messages and records dispatch outcomes.
Your application still decides what happened, who needs to know and when to send. Notify handles the email step.
Useful messages, in context
Explore three illustrative uses. These examples run only in your browser and send nothing.
Give the person who submitted a form a useful acknowledgement, and let the right team know there is something to review.
Explore Sanctum FormsYour enquiry has been received. Our team will review the details and contact you about the next step.
Turn an application event, such as a ticket assignment or status change, into a focused update with the next action clearly stated.
Explore Sanctum CoreThe application has assigned a request to your team. Open the source record to review the context and decide what happens next.
An external scheduler or reporting workflow can collect verified status information and ask Notify to email a regular digest to nominated recipients.
Data collection, scheduling and any backup-provider integration are separate implementation work.
Review the source system’s reported results, missing observations and items needing attention. Follow up in the source system where action is required.
The sending layer
Reusable Jinja2 templates separate message layout from application logic. Single and batch requests support both individual updates and multi-recipient workflows.
Connect supported email providers: Resend, Brevo, Mailjet, Amazon SES or SMTP. Configured fallback and retry handling help manage failed attempts and provider limits.
Tenant-bound API keys and explicit scopes restrict who can submit or inspect notifications. Suppression checks and signed unsubscribe support help manage recipient preferences.
Inspect notification status and retry outcomes through the API and, when enabled, an authenticated dashboard. Investigate failures without guessing which application attempted the send.
Before we connect it
Start with one real workflow. Agree the source event, audience, message and failure path before expanding.
No. Notify sends notifications. A monitoring tool, backup service or reporting workflow must supply the underlying information. Collection, scheduling, backup execution and remediation are separate responsibilities.
No. A successful dispatch records the email provider accepting the message. It does not guarantee inbox placement, a read receipt or action by the recipient. We scope failure handling and operational checks for your workflow.
No. This offering is focused on operational email dispatch, not mailbox hosting or a complete marketing automation suite. Audience selection, consent, campaign logic and lawful use remain responsibilities of the integrating application and its operator.
We scope the source application, templates, recipient rules, provider configuration and support needs with you. Implementation, hosting and email-provider charges depend on that scope. There is no universal price or free reporting package implied by this page.
Start with the message that matters
Tell us which update is missing today. We’ll work through the source event, recipients and integration with you.
Plan your first notification workflow