Conversation API returning wrong type of conversation part | Community
Skip to main content

Has anyone ever seen an issue with the conversations API returning the wrong type for a conversation part? I’m working with a customer and we’re seeing an issue where sometimes the API returns conversation parts with a type = “assignment” but it should be a “comment” or a “note”. I have an example I can share if that is helpful.

Hey Matthew! 

Shaq from the Support Engineering team! 😀

 

I’d like to take a closer look at this. Would you like to share that information here or would you want to create a ticket with us here in Support to review it closer? Let me know! 

Sure I can share it here. I’m working with our customer and one of their conversations you can see this message was sent:

But in the API the conversation part says it is type = assignment

Hello Shaq, any updates on this one? 

Thanks!

Looks like the Intercom API is returning "assignment" as the conversation part type when it shouldn’t. Could be how the API handles certain events. Try logging the full payload to spot any patterns. Also, check Intercom’s docs on conversation parts—sometimes the types aren’t super intuitive.

I’ve noticed this happens in conversations where no teammate has been assigned before a comment is made, whether manually or automatically.
 When a teammate replies to a conversation that isn’t assigned to anyone, the system automatically assigns the conversation to that teammate. In the API response, these cases are marked as "assignment" type.

Reply


Terms & Conditions