Auth Updates For Intercom. API Keys depreciated.

[christmmurphy]

Hey guys! I'm one of the Support Engineers here at Intercom! We've recently depreciated API keys so your repo here will need to use Personal Access Tokens instead. Can see more details here: https://developers.intercom.com/reference#using-personal-access-tokens

It would look something like this though:

intercom = Intercom::Client.new(token: '<access_token>');

Let me know if you have questions about this and I'd be happy to help out!

[patrickmclaren]

Hi Chris! Thanks for letting us know! We'll make this change over the next few days, then update this issue to confirm.

[christmmurphy]

Thanks Patrick! Let me know if I can help in anyway!

[skreis]

Hey @patrickmclaren – first thanks for sharing this project! I have a need to aggregate tag counts and this is a pretty great resource.

I'm curious if this is still runs as originally intended for two reasons:

1. It seems as if while the conversation model returned by intercom returns a tags property when querying an individual conversation, that list of tags is always empty.
2. Tagging seems to now exist at the user model level, rather than conversations – I'm somewhat new to Intercom, so I don't know how that behaved previous, but I imagine that from within a conversation you could apply a tag and it would then become associated with that conversation, allowing for the first item above to operate as expected.

When querying the user object, I then can see tags that were associated with the user, but the metadata about that tag is nonexistent aside from the id and name.

Since tags can be shared, when that tag was applied to a specific user is a little tough to capture without having that metadata available in this model's response.