Send draft
send_draftSend a draft email permanently to its recipients. This action cannot be undone, so verify the draft before sending.
Instructions
Sends a real email: the message a draft holds, exactly as the owner would read it in their Drafts folder. It reaches strangers' mailboxes and CANNOT be recalled, edited, or deleted once it has left — treat every call as final, and ask the person you are acting for before sending on their behalf. This is the one draft tool that causes mail to leave; save_draft, update_draft, and delete_draft send nothing. The call itself transmits nothing: the message is written down durably and a delivery pass offers it to a mail server seconds later, so the result says queued and never that anything was delivered. Call get_outgoing_email with the outgoingEmailId it answers to learn what became of the message, and cancel_outgoing_email to stop it while it is still waiting. Nothing is recomposed and nothing may be changed here: what goes out is what the draft says, so edit it with update_draft first and read what you wrote before sending. There is no idempotencyKey, because the draft is the identity: promoting one draft sends ONE message however many times you call, and a repeated call answers with the record the first one wrote rather than sending a second message. A draft addressed to nobody is refused naming that, and the remedy is update_draft rather than a second save. Everything this deployment refuses a send for is asked again now rather than when the draft was written, so a draft composed before a limit was tightened is refused by the limit that holds today, and a refusal leaves the draft exactly as it was. The draft is not deleted when this answers: the message is queued rather than sent, so the copy stands in the owner's folder until the message has actually been delivered and is taken out in the same pass that files the sent copy.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| draftId | Yes | The draftId save_draft returned for the draft you are sending. A UUID, and the whole of what this call takes: the message, the recipients, and the account are the draft's. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | How far this message has got. A fresh send is queued, meaning it is written down and has not been transmitted. A repeated call carrying an idempotencyKey already used answers with whatever the first message has reached since. | |
| queuedAt | Yes | When the send was first written down, as an ISO 8601 timestamp. For a repeated call it is when the first identical call wrote the record, not when this one was made. | |
| accountId | Yes | The configured MailFathom account identifier the message is sent as. Its Delivery configuration decides the From address, which a caller never supplies. | |
| recipientCount | Yes | How many people the message will be offered to across its to, cc, and bcc headers, after addresses named twice were reduced to one. Nobody is named. | |
| outgoingEmailId | Yes | The stable identifier of the queued message. It is what this send is known by afterwards, and an identical call carrying the same idempotencyKey answers with this same identifier rather than queueing a second message. |