# Orchestrate transactional email with nodulz

Source: https://nodulz.com/use-cases/transactional-email

Language: en

> Editorial summary. Check the source page for current prices, availability and live data.

Receive an event from your application, apply your sending conditions and use Brevo to send a transactional email.

## The day-to-day need.

Business emails rely on rules scattered across services. Understanding why a message was sent requires reconstructing the event and the decision behind it.

## Example: confirm an account activation

Your application sends an event when an account becomes active. Check the event type and recipient, send the Brevo confirmation template and record the provider response.

## Without a workflow

Sending logic lives in several services and tracking depends on each service’s logs.

## With nodulz

The event, condition, Brevo template and provider response are connected; unrelated events leave the path without an email.

## How nodulz solves the problem.

nodulz makes the send decision visible before calling the provider. The workflow prepares template variables and records the API response to trace the request.

### Filter incoming events

The webhook receives the event type and account data. The condition checks for an activation and an available recipient address; the false branch does not contact Brevo.

### Keep the template with the provider

The Brevo node uses your template ID and personalization parameters. Brevo maintains the email content while nodulz orchestrates when to send it and which data to use.

### Connect the response to the event

The PostgreSQL query records the event ID and provider response. A separate workflow can receive Brevo events to track delivery, bounces or later errors.

## From trigger to outcome.

Webhook · Condition · Brevo · PostgreSQL

## What this workflow brings.

The event, rule and send request are connected. Your team can inspect the provider response without confusing an accepted request with an actual delivery.

- A visible, explainable send decision.

- An identifiable template and its variables.

- A send request linked to its triggering business event.

## Keep control of the process.

Configure credentials, templates and a strategy for duplicate events. To track delivery, add a separate workflow fed by provider events.

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)