Skip to main content
A database-triggered email is an email workflow that starts when app data changes. For example:
  • a user row is created
  • a payment row is inserted
  • an invite changes from drafted to sent
  • an order status becomes shipped
  • a support ticket is marked resolved

​
Why use a database trigger?

The database is often the most reliable source of truth for product state. If the row exists, changed, or reached a specific value, the workflow can react to that state directly. This reduces the need to add email API calls throughout your app code.

​
How it differs from an API-triggered email

An API-triggered email starts because your app code called an email service. A database-triggered email starts because the data changed.

​
Example workflow