Connect your email platform

Point OmniLab at the email service that actually delivers your messages, so triggered sends go out from your own sending domain.

Connect the service you already send from, so triggered messages arrive from your sending domain and land in your existing reporting. Do this once per organisation.

Before you begin

You need Admin access to reach the organisation settings where this is configured.
Decide which platform sends the message — Brevo, Mailchimp, Salesforce Marketing Cloud, or another service with an API.
Get an API credential from that platform with permission to send transactional messages, and nothing more.
Have someone technical available. The connection is a Function, which is code.

Steps

Get the credential from your email platform

Create an API key in your email platform scoped to sending only. Avoid reusing an existing key that has broader access — this one will live in OmniLab, and a narrow key limits what a leak could do.

Switch to the Global Organization, open General Settings, and store the credential as a secret rather than pasting it into code. Secrets are write-only: they can be used by a Function but not read back out.

See Configure runtime and secrets.

Write the Function that calls your platform

Your developer writes a Function that takes what OmniLab hands it and calls your platform's send API. Which hook point it binds to depends on what you are building — see Transactional emails or Double opt-in.

Send a test to yourself

Trigger the action in a test campaign and confirm the message arrives — from the right sender, with the right template, and appearing in your platform's own sending log.

Check the spam folder too. A message triggered by a new integration is exactly the kind that gets filtered on the first send.

If something's blocked

The Function runs but nothing arrives. A successful run means your platform accepted the request, not that it delivered the message. Check your platform's own delivery log next.
Messages arrive from the wrong sender. The sender is set in your platform or in the Function's payload, not in OmniLab.
Everything works in test but not in production. The secret is probably scoped to one organisation. Confirm the same credential exists where the live campaign runs.

Email triggersTransactional emailsTrigger a message from a participant's action.Email triggersDouble opt-in email verificationThe other thing this connection powers.FunctionsConfigure runtime and secretsWhere the credential lives.