Optional
assignedOptional
attachmentAn array of attachments for the first timeline entry in the thread.
Use sendChat and sendCustomerChat mutations instead. Both allow you to backdate messages.
Optional
channel?: InputMaybe<ThreadChannel>The channel to create the thread for. Currently supported: API, EMAIL, SLACK. Defaults to API.
Optional
channelChannel details for the thread, required if channel is SLACK.
Optional
components?: InputMaybe<ComponentInput[]>The components used to create the first timeline entry in the thread.
Use sendChat and sendCustomerChat mutations instead. Both allow you to backdate messages.
The identifier of the customer being either the existing customer ID, the customer's email address or and external ID.
Optional
description?: InputMaybe<Scalars["String"]>The optional description for this thread. This is used to display a preview of the thread in the UI. If not provided, we will automatically infer it from the components you provided.
Optional
externalThe external ID of this thread. You can use this field to store your own unique identifier for this thread.
Optional
labelAn array of label types to attach to the thread upon creation.
Optional
priority?: InputMaybe<Scalars["Int"]>The priority of the thread. Valid values are 0, 1, 2, 3, from most to least urgent, defaults to 2 (normal).
Optional
tenantA thread may be assigned to a specific tenant.
Optional
threadAn array of thread fields to attach to the thread upon creation.
Optional
title?: InputMaybe<Scalars["String"]>The title of the thread.
User or machine user this thread should be assigned to.