Tips for Developers

Hey everyone 👋 My name is Ivan and I’m a Customer Support Engineer here at Intercom. You might’ve seen my face around if you messaged our support via the Messenger 👷🏼‍♂️ Here’s a sample Python scrip you can use to copy your articles from your US to your EU workspace 👇import requests# set parameters for US and EU endpoints/headersintercom_token_us = "<YOUR US TOKEN GOES HERE>"intercom_token_eu = "<YOUR EU TOKEN GOES HERE>"intercom_us_url = "https://api.intercom.io/articles"intercom_eu_url = "https://api.eu.intercom.io/articles"# header used to get the articles from US workspaceintercom_headers_us = { "Authorization": "Bearer " + intercom_token_us, "Accept": "application/json", "Content-Type": "application/json",}# header used to create the articles in EU workspaceintercom_headers_eu = { "Authorization": "Bearer " + intercom_token_eu, "Accept": "application/json", "Content-Type": "application/json",}# store all articles in a listarticles = []# get all ar

Hey there! Ebenezer here from Engineering Support👋.We get a lot of questions on how to “Pass a Company ID over in a Conversation”. While Company data doesn't get stored in the Conversation Object, there is a way to do this!☝😎First, you'll need to create a Conversation Data Attribute that stores the specific value that you're looking to access.Next, Your team will need to perform several calls to our REST API to get the ball rolling. Initially, they would Retrieve a conversation and then locate the value for  source.author.id. This value will contain the ID of the person who initiated the conversation.A little side note; You’ll want to verify that the source.author.type is "user" for those conversations. If it's "admin" then that ID will be for a team member on your workspace who started the conversation. In these situations, you will want to dig into the conversation_parts attribute to see who the actual customer is.Once you have the ID of the User, you will then want to make a call

Hey Support Leaders 👋 I’m Michelle, and I’m a Support Manager here at Intercom.  I wanted to share some insight into something we’ve been working on within our Support team over the last few months that I think might be useful to others across the industry. With customers all over re-evaluating their tech stacks and looking to minimise costs where possible, it’s more important than ever to ensure that they are getting the most out of your product, and really getting to see the value it has, to help inform their decision making.  At Intercom, we spotted an opportunity to utilise our own Support team (who are speaking with hundreds of customers every day), to proactively flag with customers when they are not using features within their subscription (that they’re paying for!), so that they can see the full power of what they can do with Intercom.  The problem we faced, like most Support teams, is that we did not have a tonne of capacity to spare for our team to take on the additional wor

Hey, I’m B, a Customer Support Engineer with Intercom 👋🐝 An issue we often see users face when building Product Tours & Tooltips is that their selector cannot be found on the page the Tour is being built on.A guaranteed way of making your Product Tour display as expected is editing your CSS selectors to the Intercom specific ones provided -[data-intercom-target="Specific element name"]You’ll find more on this method in this article from our Help Center 📌 

When managing conversation history, it’s not uncommon for Intercom customers to need to export the full contents of a Conversation from Intercom into a third party tool. Depending on the information needed there are a few different approaches to take.  If you don’t need the full text of the Conversation, rather you only need to export the data around the text (ex. which customer you’re speaking to, which admin handled the conversation, etc) then there are 2 different ways to get this data.Option 1: Via the Data Export option in our Reports 1). In the Reports section of your Intercom workspace click on the Data Export option, click on the Conversations or the Tickets tab (depending on which you want to export), and choose your timeframe and any filters that you want to use.2). Choose which fields you want to include in the export from the 4 dropdown menus under the Select Fields to Export section.3). Click on the Export CSV button. An email with a CSV file of those Conversations will be

Using our JS API, it is not possible to update the email field of a visitor type contact with the standard Intercom('update', {"email": "rk.test@testing.com"}); Doing so will result in a 403 error. However, using a parameter in the JS API called anonymous_email will allow you to convert a visitor to a lead via the JS API without running into any issues. Use the update method to pass through the email of the visitor without needing to set up REST API calls to achieve the same result. Intercom('update', {"anonymous_email": "test@example.com"});

Proactive Support Messages can be set to only display on a specific URL in the Where to send section of the settings. This is really useful for delivering content to end-users on the page that is relevant to the message. However, this can pose an issue for users on mobile devices where the Intercom SDKs are installed as there is no specific URL that can be targeted. As a workaround for this, a custom attribute can be set up for tracking the screen that the mobile user is currently viewing. By sending this data to Intercom and storing it in an attribute, it's possible to send messages targeted to mobile users on a specific mobile screen that they are currently viewing. To do this -  Create a custom attribute - for example, called 'current_screen'. This will be used to store the data which is sent to Intercom each time the user navigates to a new screen in your mobile app. This can be done for all screens in your app or just the ones that require targeted Intercom messages.  Implement