Removal of clientMutationId field from several Ink mutations, including CreateInkInboundMessage

Action Required

Sept. 30, 2025, 8:38 a.m.

What is changing?

Several Ink API mutations (AssignInkBucket, UpdateMessageTags, CreateInkInboundMessage, AddNoteToInkConversation) are providing the clientMutationId GraphQL field. However, this field is unused (as it returns no data when requested).

As such, we're removing it to decrease confusion regarding available data on those mutations

Timeline

The removal date is set for the 20th of October 2025.

What do I need to do?

Please stop using the clientMutationId field, a validation error will be raised if there are attempts to access it once it has been removed.