Transactional emails
Send emails from your own platform when a participant acts, such as a sign-up, a reward won or a confirmed booking.
1 min read
A transactional email goes to one person at one moment, because of something they did. A marketing email goes to a whole list.
The campaign's own notifications already cover participation, winners and booking confirmations, reminders and cancellations, with no code: see Two kinds of email. This page is for emails your own platform sends.
What can trigger your own email
| Moment | Event | Connect it with |
|---|---|---|
| A participant signs up | contact.created.v1 | A platform event Function or a webhook |
| A participant wins a reward | reward.won.v1 | A platform event Function or a webhook |
| A participant completes a touchpoint | touchpoint.completed.v1 | A platform event Function or a webhook |
| A booking is confirmed | ticket.confirmed.v1 | A webhook |
| A reminder before a booking | No event: schedule it in your platform, from the booking it received | Your platform |
A Function sends the email from OmniLab, through your platform's API: see Platform event functions. A webhook sends the event to your own system, which sends the email: see Configure webhooks.
Decide before your developer starts
- Which moments trigger an email, from the table above.
- Which platform sends them: your email service provider, your CRM or a dedicated transactional tool.
- What each email shows: the participant's name, the event details, the reward description.
- Who designs and writes the email templates.