email.sent

​

Payload

{
  "id": "whd_3Pv6nW8kD",
  "event": "email.sent",
  "createdAt": "2026-09-11T14:20:09.402Z",
  "data": {
    "messageId": "18f2d6b1c9e04a7d",
    "threadId": "18f2d1c04b7e9a23",
    "channelId": "chan_4Kp8wN",
    "conversationId": "conv_3Hq9rT",
    "from": "maya@acme.com",
    "fromName": "Maya Chen",
    "to": ["ada@ravennafoods.com"],
    "cc": [],
    "subject": "Re: Pricing for the Ravenna rollout",
    "receivedAt": "2026-09-11T14:20:05.000Z",
    "folder": "SENT"
  }
}

​

When it fires

• The sender is one of the workspace’s connected mailboxes, a teammate’s included, whichever connected mailbox the copy turns up in.
• The thread is a conversation. A message in a thread that is already a conversation counts. A new outgoing thread counts when the New mail handling setting turns it into one, judged on its recipients, so mail sent only to teammates never counts.

​

What sends nothing

• A repeat of the same message. Custral skips a message it has processed in the last five minutes, so a message that lands in several connected mailboxes, such as the sender’s copy and a copied teammate’s, is delivered once.
• A message in a spam folder. Mail the provider files as spam or junk sends no email event at all.
• Replies from a forwarding address. When a mailbox forwards its incoming mail to another address, a reply sent from that address is handled by the forwarding and usually sends nothing.

​

Worth knowing

• Opens and clicks are separate events, and only for mail a workflow or a sequence sent: email.opened and email.clicked.
• No body. Read the message itself from the conversation through the Conversations API.
• Ids belong to one mailbox. Each connected mailbox has its own messageId and threadId for the same mail. Key on conversationId to follow a conversation.

​

Example

custral.on("email.sent", async (event) => {
  const {from, to, subject, conversationId} = event.data;

  await activity.logOutbound({from, to, subject, conversationId});
});