Skip to main content
Using TypeScript? Check out our GraphQL SDK for a fully typed client.
Thread fields allow you to extend Plain’s thread data model. The thread fields which you want to support have to conform to a schema configured in Settings → Thread fields. Thread fields can be nested and be either a boolean, text or a string enum. Thread fields can be required. When they are required, their value must be set in order for the thread to be marked as done. For interacting with thread fields via the API, every field has a key defined in its schema. Keys make it possible to quickly refer to a thread field without having to know its ID in the schema. For example if you have a field called “Product Area” the key you might choose for the key to be product_area.

​
Upsert a thread field

To upsert a thread field you need an API key with the following permissions:
  • threadField:create
  • threadField:update
Mutation
mutation upsertThreadField($input: UpsertThreadFieldInput!) {
  upsertThreadField(input: $input) {
    result
    threadField {
      id
      key
      type
      threadId
      stringValue
      booleanValue
      isAiGenerated
      createdAt {
        iso8601
      }
      updatedAt {
        iso8601
      }
    }
    error {
      message
      type
      code
      fields {
        field
        message
        type
      }
    }
  }
}
Variables
{
  "input": {
    "identifier": {
      "threadId": "th_01HVNWFJS395XVPPBJNE6A8BHP",
      "key": "product_area"
    },
    "type": "STRING",
    "stringValue": "security"
  }
}

​
Delete a thread field

To delete a thread field you need an API key with the following permissions:
  • threadField:delete
Mutation
mutation deleteThreadField($input: DeleteThreadFieldInput!) {
  deleteThreadField(input: $input) {
    error {
      message
      type
      code
      fields {
        field
        message
        type
      }
    }
  }
}
Variables
{
  "input": {
    "threadFieldId": "tf_01HVTN2VTNYP91P5XGDQ57M2ZX"
  }
}