ESHOPMANESHOPMAN Logo
Our Blog

HubSpot's Help Desk Update: Say Goodbye to Comments, Hello Notes (and What it Means for Your E-commerce Integrations)

HubSpot's Help Desk Update: Say Goodbye to Comments, Hello Notes (and What it Means for Your E-commerce Integrations)

Hey ESHOPMAN community! If you're a HubSpot user, especially one deeply involved in RevOps, marketing, or managing an e-commerce store with HubSpot at its core, then you know how critical it is to stay on top of platform changes. Recently, a discussion in the HubSpot Community caught our eye – a heads-up about a significant upcoming shift in how internal conversations are handled within the Help Desk. It’s an update that might seem small on the surface, but for anyone running integrations, it’s a big deal.

The Big Change: Comments are Becoming Notes in Help Desk

The original poster, a HubSpot representative, laid out the details: HubSpot is transitioning away from "thread comments" in the Help Desk and moving towards a more unified system using "notes." The goal? Consistency. HubSpot wants the experience of adding internal discussions to be the same across the board, whether you're logging something on a CRM record or discussing a customer ticket in Help Desk.

This isn't just a UI tweak; it has significant implications for developers and anyone with integrations relying on the Conversations API. Specifically, the POST /conversations/v3/conversations/threads/{threadId}/messages endpoint, when used with "type": "COMMENT", will stop working for Help Desk threads.

When Is This Happening? Mark Your Calendars!

You’ve got some lead time, but don't procrastinate! Integrations will start receiving errors when attempting to create comments on Help Desk threads beginning on September 23, 2026. That might seem far off, but for complex e-commerce setups with multiple integrations, planning and testing take time.

Here’s the error message you’ll start seeing if your integration isn't updated:

{
    "status": "error",
    "message": "Publishing comments to HelpDesk threads is prohibited via this API. Please consider using the Notes API for inbox 1501388101",
    "correlationId": "1025cbcb-95f9-4deb-b252-c8caa3a47b45",
    "context": {
        "inboxId": [
            "1501388101"
        ]
    },
    "category": "VALIDATION_ERROR",
    "subCategory": "ConversationsApiError.HELPDESK_INBOX_CANNOT_PUBLISH"
}
 

What This Means for Your E-commerce Integrations and How to Adapt

For those of us integrating customer service channels into HubSpot – whether it’s email, live chat, or even messages from an online WhatsApp store builder – this change is crucial. Internal team notes are vital for context, collaboration, and ensuring a seamless customer experience, especially when dealing with e-commerce orders, returns, or product inquiries. If your current setup uses the deprecated method, you need to pivot.

Your Action Plan: Switch to the CRM Notes API

The solution is clear: move to using HubSpot’s CRM Notes API. Here’s the gist of what you need to do:

  1. Create Notes: Instead of using the Conversations API for comments, you'll now use the CRM Notes API to create new notes.
  2. Associate Notes with Tickets: Once created, these notes need to be associated with the relevant ticket. You can do this using the CRM Associations API. The ticket ID can be found in the thread details (specifically, associatedTicketId).
  3. Reading Existing Data: If your integration also reads existing comments, you should update it to instead retrieve the notes associated with the ticket.

How do you know if a thread is in a Help Desk inbox versus a regular conversation inbox? You can check for the error message above, or programmatically determine the inbox type:

  • Get the originalChannelAccountId from the thread details.
  • Use that ID to get the inboxId for the channel account.
  • Finally, check the type property in the inbox details. If it's "type": "HELP_DESK", you know what to do!

It's important to note that existing comments will remain visible in Help Desk even after the migration to notes is complete, but they won't be automatically converted into the new note format. So, historical context will still be there, just in its original "comment" form.

The Community Weighs In: Exporting Notes and Regulated Industries

One astute community member immediately raised a critical question: "Does this mean that the threaded notes will be able to be exported via the API endpoint now/exposed to the API?" They highlighted a past pain point for organizations in highly regulated industries, where the inability to easily export notes has been a functional gap.

While the original announcement didn't directly answer this follow-up, the shift to using the CRM Notes API for creation and association strongly implies that notes are now fully integrated into the CRM object model. This means they are inherently more accessible and manageable via the CRM API, including for retrieval and, by extension, export. For businesses in regulated sectors, this consolidation into a standard CRM object should be a welcome improvement, making audit trails and data retention much more straightforward.

ESHOPMAN Team Comment

This move by HubSpot is a smart strategic play for consistency, and we fully support it. While it means a bit of rework for developers and RevOps teams managing integrations, the long-term benefit of having a unified "notes" object across all CRM records, including Help Desk tickets, far outweighs the short-term effort. For e-commerce businesses, clear internal communication on customer tickets is paramount, and standardizing this process will only enhance data integrity and team efficiency. We specifically appreciate the implied improvement for data accessibility, which is crucial for compliance and internal reporting.

In essence, this update is about bringing more structure and consistency to your internal team communications within HubSpot. For e-commerce businesses, where customer inquiries can range from simple order tracking to complex technical support, having a robust, unified system for internal notes is invaluable. It ensures that every team member, from sales to support, has the full context of a customer interaction, regardless of the channel it originated from – be it email, chat, or even customer queries from your online WhatsApp store builder.

So, take this heads-up seriously. Start planning your integration updates now to ensure a smooth transition well before September 2026. Your future self, and your entire customer-facing team, will thank you for it!

Share: