- GET /conversations/v3/conversations/threads is always ascended sorted, which means you have to page from the first message to the last. This seems like the exact opposite of the most useful case where you want to automate some inbox handling. You want then to page through from newest to oldest and stop when you are done with your processing
- PATCH /conversations/v3/conversations/threads/{threadId} the docs say you need to specify the threadId in the parameters (again) but that doesn't seem to be the case. Which is good because it would be weird 😛 - PATCH /conversations/v3/conversations/threads/{threadId} only allows setting status and archived. This is too limited for much use I think. Associate contacts, or assign is what I am looking for right now for example. - GET /conversations/v3/conversations/threads/{threadId} doesn't give me the assigned user back, nor any relevant deals. - There doesn't seem to be a way to programmatically create an inbox item. I wanted to work around this by sending an email, then programmatically assign it to the correct user, and connect to the right customer, and to the right deal. But due to the issues above I can't seem to be able to do that...
Could someone please help me understand why it is not possible (at least based on the api spec/docs) to start new threads (i.e. compose new emails) via conversations api? I took a look at which api is used when an email composed in the inbox is sent and it is not conversations api.
Besides there is a note in the api spec that it is not possible to create/start new threads, so I wonder what could be the reason for not exposing/adding an api for starting new threads.
Hi @boxed , thanks for taking the time to give us feedback! Would you be willing to tell us more about the applications you are trying to build and customer use cases behind them such that have led you to want more from reading and updating converstaions, and especially the last one where you want to 'create a new inbox item'? Thanks much, The Product Manager
The inbox is a fairly natural task queue. I have an external system which would like to put things in that task queue. But there is no way to make those emails assigned to a specific user and deal.
Some options: - the API could allow me to do it, so I'd build a cron job that goes through new emails and sort them based on the content of the email (which I supply so I can know what is in there). This not very good, but was what I was hoping to do. 😛 - create items directly in the inbox, with connections to users and deals through the API - hubspot respecting some special email header that you could use to do this tagging. For example `X-HubSpot-Deal` and `X-HubSpot-Assignee` would be great. This would imo be the best solution, and would make integration work super easy.
