Drafts

Org: GET /v0/emails/drafts, /v0/emails/drafts/:id · Inbox: full CRUD under /v0/emails/inboxes/:inbox_id/emails/drafts… · Project: list/get.

Create

Plain, reply, reply-all or forward drafts from one body:

{ "to": ["u@e.com"], "subject": "Review this draft", "text": "Draft body",
  "client_id": "your-stable-workflow-id",
  "attachments": [{ "filename": "a.pdf", "content": "<base64>" }] }

Reply: set in_reply_to — recipients/subject/threading derive from it.
Forward: set forward_of — body and attachments merge in at send time.
in_reply_to and forward_of are mutually exclusive; reply_all forbids to/cc/bcc.

Update & send

PATCH supports nullable field clears, add_attachments / remove_attachments, add_labels / remove_labels, and send_at changes. POST …/:id/send delivers the draft (forward content merges at that moment) and deletes it — the returned object is the sent email.

Scheduled sends

A future send_at marks the draft scheduled. The Worker cron (every 5 min) sends due drafts. Creating a schedule or editing a draft while its schedule remains active requires draft_send, in addition to the create or update permission. A draft-only key may cancel the schedule with send_at: null and keep the result as an ordinary draft; it cannot schedule an outgoing message. Scheduled-send failures are rescheduled for a later cron attempt. A failed immediate-send request records failed; inspect the result before repeating an action whose provider outcome is uncertain. The original autonomous-registration key retains its draft-only restrictions after human workspace claiming.

Start

Email

Realtime

Phone and compute

Network

Platform

Build

Roadmap

Drafts

Drafts

Create

Update & send

Scheduled sends

​Drafts

​Create

​Update & send

​Scheduled sends

Drafts

Create

Update & send

Scheduled sends