Skip to main content
MailerPath supports two distinct paths for sending emails to contacts:
  1. Transactional send: triggered immediately by your application for a single recipient.
  2. Workflow send: orchestrated automatically by MailerPath when a contact qualifies for a workflow step.
Use this section to understand how each path works, how to trigger a transactional send, and how to read sent email statuses and delivery history.

​
Which path to use

Use caseSend path
Order confirmation, password reset, alertTransactional send
Onboarding series, re-engagement, renewalWorkflow send
One-time announcement to a segmentCampaign

​
How transactional send works

  1. Your application calls POST /client/send with a template and recipient.
  2. MailerPath resolves the contact, applies template variables, and dispatches to the provider.
  3. A sent email record is created with a unique ID and initial status.
  4. Status updates (delivered, opened, clicked, bounced) flow in from provider webhooks.

​
How workflow send works

  1. An event triggers a workflow for a qualifying contact.
  2. MailerPath checks suppression rules, rate limits, and send windows.
  3. The email is queued and dispatched when conditions are satisfied.
  4. Outcome is tracked at the execution and sent email level.