Drafts, scheduled sends, and cancelling

Stage a message before it goes, schedule it for later, and cancel it before it sends.

Mails.ai — Drafts, scheduled sends, and cancelling

A draft is a message that exists but has not been sent. Saving one checks only its fields and your draft limit. The firewall, the suppression list and your sending limits run when it is sent, so a scheduled draft can still be refused at its send time. Press Send test in the composer to see the firewall's verdict first.

The Drafts page: a draft, a scheduled send that is due now, one sent and one that failed

The lifecycle

  1. POST /v1/drafts creates it. Status draft, or scheduled if you set send_at.

  2. PATCH /v1/drafts/{id} edits it — subject, body, recipients, send_at — while it is a draft or scheduled.

  3. POST /v1/drafts/{id}/send sends it now.

  4. Or set send_at and the scheduled dispatcher sends it at that time. Status scheduled.

Cancelling

POST /v1/messages/{id}/cancel stops a message sent with scheduled_at that has not gone yet. To stop a scheduled draft, clear its send_at with PATCH /v1/drafts/{id}, which makes it a plain draft again, or delete it. Once a message is sent it cannot be recalled — email does not work that way.

Events you can subscribe to

Drafts emit their own events: draft.scheduled, draft.sending, draft.sent and draft.failed. Subscribe to draft.failed to hear when a scheduled draft was refused or failed at its send time. A message sent with scheduled_at that is refused at its send time emits message.failed, carrying the reason.

Open drafts are capped per plan — 1,000 on Free, 10,000 on Pro, 50,000 on Scale.

Open drafts
Did this answer your question?
😞
😐
😁