UNPKG

intercom-client

Version:

[![fern shield](https://img.shields.io/badge/%F0%9F%8C%BF-Built%20with%20Fern-brightgreen)](https://buildwithfern.com?utm_source=github&utm_medium=github&utm_campaign=readme&utm_source=https%3A%2F%2Fgithub.com%2Fintercom%2Fintercom-node) [![npm shield](ht

27 lines (26 loc) 1.54 kB
/** * This file was auto-generated by Fern from our API Definition. */ import * as Intercom from "../index"; /** * The Conversation Part that originated this conversation, which can be Contact, Admin, Campaign, Automated or Operator initiated. */ export interface ConversationSource { /** This includes conversation, email, facebook, instagram, phone_call, phone_switch, push, sms, twitter and whatsapp. */ type: string; /** The id representing the message. */ id: string; /** The conversation's initiation type. Possible values are customer_initiated, campaigns_initiated (legacy campaigns), operator_initiated (Custom bot), automated (Series and other outbounds with dynamic audience message) and admin_initiated (fixed audience message, ticket initiated by an admin, group email). */ delivered_as: string; /** Optional. The message subject. For Twitter, this will show a generic message regarding why the subject is obscured. */ subject: string; /** The message body, which may contain HTML. For Twitter, this will show a generic message regarding why the body is obscured. */ body?: string; author: Intercom.ConversationPartAuthor; /** A list of attachments for the part. */ attachments?: Intercom.PartAttachment[]; /** The URL where the conversation was started. For Twitter, Email, and Bots, this will be blank. */ url?: string; /** Whether or not the source message has been redacted. Only applicable for contact initiated messages. */ redacted: boolean; }