Skip to main content

Outbound Email Adapter

Our Current Assumptions (Need Confirmation)​

Assumption 1: TwoWay Field → Email Field Mapping​

Currently Email Service Required these body parameter as required field Request Parameters

We assume the email adapter receives TwoWay fields as follows:

TwoWay FieldContainsExample
Chat.ConversationClientIdCustomer's email (who sent the original email) (To)[email protected]
Chat.ConversationHostIdSender address from customer's verified domain (From)[email protected]
Chat.ConversationHostNameDisplay name (Required for From object in email API)Agent Assist

  • Is this mapping correct?

  • Is it possible to have a dedicated message type for email in Two Way?

To make the email mapping explicit and avoid relying on overloaded fields, we propose adding email $type to the TwoWay format:

Add Email-Specific Message Type:​

{
  "conversationMessages": [
    {
      "$type": "email",
      "subject": "Re: Order #123",
      "text": "Hello, your order is confirmed.",
      "html": "<h1>Hello</h1><p>Your order is confirmed.</p>",
      "attachments": [
        {
          "fileName":"Name of the file with extension",
          "content":"Base64 encoded file content",
          "contentType":"MIME type of the file"
        }
      ]
    }
  ]
}