One-off emails are sent once to a group of your contacts. Unlike automatic emails, you send them yourself — for newsletters, announcements, and promotions. The API and some buttons call them broadcasts.

Creating a one-off email

Go to Emails → One-off and click New one-off email.

Give it a name (internal only — not shown to recipients).

Select an email template. If you don't have one yet, create it in Emails → Templates — you can write it from scratch or generate it with AI there.

Select your audience. See below for the available audience types. The audience count ("X leads will receive this") updates automatically as you change the selection — it excludes unsubscribed contacts.

Click Create broadcast. It is saved as a Draft.

On its card, click Send now and confirm. Sending begins immediately.

Previewing before you send

Two preview tools sit on the form so you can verify both the message and the audience before hitting send:

Preview email (next to the template selector) renders the email exactly as recipients will see it, with merge tags like {{lead.name}} resolved using a real contact from your org.
See recipients (next to the audience selector) opens a list of the actual contacts that will receive it — names, emails, and the widget they came from.

Audience types

Everyone — every contact in your org with a valid email address.
By widget — only contacts from a specific widget.
By site — all contacts captured from any widget on a specific site.
By tag — contacts that have been assigned a specific tag.

Unsubscribed contacts are always excluded

Regardless of the audience filter, contacts marked as unsubscribed (either manually or by clicking the unsubscribe link) are never included in a one-off email.

Status

Draft — created but not yet sent. Can be edited, duplicated, or deleted.
Sending — currently being sent in batches. Cannot be canceled once started.
Sent — all batches processed. Shows recipient count, delivered count, and failed count. Can be duplicated or deleted.
Failed — every email in the send failed. Click Try again to retry the same audience, or check the inline failure reason.

Edit, duplicate, retry

Edit — update the name, template, or audience of a draft before sending. Sent ones can't be changed, so the history stays honest.
Duplicate — copy any one-off email as a new draft with the same template + audience. Use this to send one again.
Try again (failed only) — re-runs the send against the same audience. The previous failure reason and counts are reset before retrying.

How sending works

When you confirm, the status atomically transitions to Sendingso the same one-off email cannot be sent twice. Contacts are fetched, personalized, and sent in batches of 100 via the Resend API. Each email includes the recipient's name and widget in the subject/body via template variables, plus a footer with an unsubscribe link.

The From address uses your organization's name: Your Org Name <noreply@uptodatewebdesign.be>.

Send a one-off email from the API

Any saved one-off email can be turned into a reusable webhook target. Each call clones it (template + audience), sends it immediately, and creates a new entry in your History — so every send is logged with delivery counts and failure reasons.

Open the one-off email and click API trigger → Enable trigger.

Copy the generated webhook URL.

Generate an API key from Developers → API keys.

POST to the URL from your own server with Authorization: Bearer YOUR_API_KEY.

curl -X POST https://your-domain.com/api/v1/broadcasts/btr_XXXX/send \
  -H "Authorization: Bearer YOUR_API_KEY"

The response includes the cloned broadcastId, plus recipientCount, sentCount, failedCount, and failureReason. Sends made this way appear in History with a via API badge. Click Regenerate URL to rotate the token (the old one stops working immediately).

One-off emails vs the /api/v1/trigger endpoint

The trigger above sends to the audience saved on that one-off email. If you instead want to send to contacts matching arbitrary data criteria from your own payload, use the stateless /api/v1/trigger endpoint documented in Integrations.

Bounce and complaint handling

When Resend reports a hard bounce or a spam complaint, MyVisitors automatically marks the corresponding contact as unsubscribed. They will not receive future one-off or automatic emails. No manual action is required.

One-off emails cannot be unsent

Once you confirm sending there is no way to cancel or recall the emails. Use the audience size preview to double-check the recipient count before confirming.

Deleted templates

If the email template attached to a draft is deleted, its card will show Template deleted in red and the Send now button will be disabled. Create a new template and a new draft to proceed.