About email triggers
Understand which emails OmniLab sends, which ones your own email platform sends, and where the line between them sits.
Send the right message the moment a participant does something — signs up, wins a prize, books a slot — without anyone watching a dashboard. This page explains what OmniLab sends on its own and what needs your email platform, because that distinction decides how much setup you need.
Two kinds of email
| Campaign notifications | Triggered emails through your platform | |
|---|---|---|
| Sent by | OmniLab | Your own email platform |
| Looks like | An OmniLab notification, styled to your campaign | Everything else you send |
| Set up in | The campaign itself | A connection plus a small piece of code |
| Use it for | Confirmations, reward messages, booking reminders | Anything that must match your other emails, or reach your own automations |
If you only need a participant to receive a confirmation or a reward message, campaign notifications do that on their own — see About notifications. Everything on this page is for the second case.
When you need your own platform
- Deliverability matters. Your platform already has a warmed sending domain and an established reputation.
- The message must match your other emails. Same template, same footer, same unsubscribe.
- The send should enter your existing automations. A sign-up should start a welcome series you already run.
- You need the sending record where your team looks. Support staff check your platform, not OmniLab.
How it fits together
OmniLab decides when something should be sent and hands over the details. Your platform decides how it looks and actually delivers it. The join between them is a small piece of code — a Function — that calls your platform's API.
That split is why two things on the next pages both need a Function: sending a triggered message, and confirming an address in double opt-in.
A Function is a developer task, once
Someone technical writes it once per email platform and it then serves every campaign in the organisation. Marketing teams do not touch it again unless the platform changes. See About Functions.