How does Notify work for sending transactional email from an application?

“Notify” usually refers to a notification/email service that your application calls through an API to send transactional messages like password resets, order confirmations, OTPs, receipts, and alerts.

How it works

1) Your app triggers an event

Something happens in your application, for example:

• a user signs up
• a password reset is requested
• an order is placed
• a payment succeeds

Your backend then decides to send an email.

2) Your app calls Notify’s API

Instead of sending email directly via SMTP, your app makes an API request to Notify with:

• recipient email address
• template ID or message content
• personalization data
• sender information

Example flow:

• App detects “password reset requested”
• App sends a request to Notify with the reset link and user email
• Notify queues the message for delivery

3) Notify renders the template

If you use templates, Notify takes the template and fills in variables such as:

• user name
• order number
• reset link
• expiry time

This keeps email content consistent and easy to manage.

4) Notify sends the email

Notify handles the actual email delivery through its mail infrastructure:

• queues the message
• attempts delivery
• retries if needed
• tracks delivery status

5) Your app can track status

Depending on the service, you may get:

• sent
• delivered
• bounced
• failed

Some systems also provide webhooks or logs so your app can respond to delivery events.

---

Why use Notify for transactional email?

• Reliability: built for fast, dependable delivery
• Scalability: handles spikes in email volume
• Templates: easier to manage standard messages
• Security: avoids exposing SMTP credentials in client-side code
• Observability: logs, status, and delivery tracking
• Separation of concerns: your app handles business logic; Notify handles sending

---

Typical architecture

1. User action in app
2. Backend service creates email payload
3. Backend calls Notify API
4. Notify sends email
5. User receives email
6. App logs result / handles webhook updates

---

Example use cases

• account verification
• password reset
• two-factor authentication codes
• invoice emails
• shipping notifications
• security alerts

---

If you mean a specific product named Notify (for example, a government or cloud notification service), I can explain that exact workflow too—just tell me which Notify you’re using.