Reply to api initiated conversation not working about intercom-node

[davidseek]

and who should we poke to get this done?

[davidseek]

Is there any new development on that? It has been 1yr+ and we're right now in the need of a fix for that.

[kant01ne]

when creating an admin initiated message from the API like in the example below you are not actually creating a conversation but a message. The id (id: '106118468' in the example below) refers to the message which explains why you are getting a 404 when trying to fetch/reply to a conversation using this message_id.

var message = {
  message_type: "email",
  subject: "Hey",
  body: "Ponies, cute small horses or something more sinister?",
  template: "plain",
  from: {
    type: "admin",
    id: "343616"
  },
  to: {
    type: "user",
    id: "588a21cc7b1ed4f39f0bf2dd"
  }
}

client.messages.create(message, callback);

returns:

body: 
   { type: 'admin_message',
     id: '106118468',
     created_at: 1496756108,
     subject: 'Hey',
     body: 'Ponies, cute small horses or something more sinister?',
     template: 'plain',
     message_type: 'email',
     owner: 
      { type: 'admin',
        id: '343616',
        name: 'Kevin Antoine',
        email: '[email protected]',
        avatar: [Object] } },

The reason why we do not return the conversation_id is that a conversation is not always created when a message is created. This is a limitation of our Engage product that allows sending messages from an admin to X-users. It wouldn't make sense to create a conversation for each outbound messages sent.

A conversation is created only for user-initiated messages. In this case, your workaround using /last/reply is a good workaround/hack. We are going to look into how we can return the conversation_id from the API in this case but I can't give an ETA right now.

[Jolg42]

Hi @Skaelv
Great! This would be better than the current hack :)

[kant01ne]

This is in our backlog for API improvement. I'll close this one as this is related to our API and not specific to intercom-node.
Thanks for reporting this @Jolg42

[illyavorobets]

any updates with it?