Popular Topics

HiI know that I need to use the API to export articles, and I’ve looked at a couple of existing questions around this. The answer seems to be, you need to use the API and to look at the article Formatting and exporting your articles with the API for answers. That article doesn’t have any information about exporting articles using the API. It has one line of text right at the bottom, pointing you to the developer docs, but not guidelines as to how to start.  I looked at the data export section of the developer docs and gave that a try, and first of all found out that it will only pull data from a 90 day period, so pretty useless if you want to export docs that have been created over time. I tried the Export API endpoint with a shorter time period and still had issues. For anyone else trying, you first have to Create a Data export, the response from that request will give you a job number. You then need to download the data export, using the job number.I tried this in the Intercom test e

In case we have a custom launcher on a web app or site, will this https://developer.chrome.com/en/docs/privacy-sandbox/third-party-cookie-phase-out/ (From January Chrome will stop supporting third-party cookies) affect the proper functioning of the launcher and the utilization of the chat box?Thank you!

Hi all, I saw this post somewhat related to what i’m about to post it’s not the same. Essentially, Chrome is not allowing 3rd party cookies so I was wondering if there’s anything we need to take into account for Intercom as we’re a current Intercom customer.  Intercome’s error:> Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies.

I have been using the Intercom API to try to recreate the regular metrics in Metabase. I have tried using this resource but haven’t found it to be particularly helpful. For example, if I try this query, the response maps to the New Conversations Metric in the Intercom dashboard instead of the Assigned Conversations metric which is my intention. SELECT  "Inbox Details - Team Assignee"."inbox_name" AS "Inbox Details - Team Assignee__inbox_name",  COUNT(*) AS "count"FROM  "public"."conversations_data" LEFT JOIN "public"."inbox_details" AS "Inbox Details - Team Assignee" ON "public"."conversations_data"."team_assignee_id" = "Inbox Details - Team Assignee"."inbox_id"WHERE  (    (      "Inbox Details - Team Assignee"."inbox_name" = 'VIP Support Inbox'    )       OR (      "Inbox Details - Team Assignee"."inbox_name" = 'Support'    )    OR (      "Inbox Details - Team Assignee"."inbox_name" = 'VIP Escalation Inbox'    )    OR (      "Inbox Details - Team Assignee"."inbox_name" = 'Escalation I

How have you gone about it? We are currently using Salesforce Service Cloud as our primary Support ticketing solution and have tried Intercom's out of the box integration. However, its hard to get chat transcripts to sync properly to the CASE opposed to being a task with a CONTACT. Eventually, we would like to use Intercom as an interface for customers to easily create cases on their own, as an alternative to Custom/Resolution bots and Chat based triage - which right now is very manual (as Cases are created from the Inbox by an Employee). Also, we are looking into building out some webhooks to sync Account based details more easily, as the User centric model doesn't work well for our B2B product. Anyone in the same boat, that may have similar use cases, that have built out a solution? Curious to hear from others.

Hello, We created a custom attribute with the list type called `Channel Networks`. When we try to update it via the API we get back the following error:```{  type: 'error.list',  request_id: 'REDACTED',  errors: [    {      code: 'nested_custom_attributes',      message: 'Cannot submit an array as a custom attribute value'    }  ]}```Other custom attributes work fine, just list/array type ones fail.```const respIntercom = await fetch(`https://api.intercom.io/contacts/${contact_id}`,{method: 'PUT',headers: {'Content-Type': 'application/json','Intercom-Version': '2.12',Authorization: `Bearer ${process.env.INTERCOM_ACCESS_TOKEN}`},body: JSON.stringify({"name": userData.user.name + " TEST","phone": userData.user.phone,"last_seen_at": userData.user.last_online,"signed_up_at": userData.user.created_at,"custom_attributes": {"ACME": userData.user.acme,"Channel Networks": ["Channel 1", "Channel 2"],}})});```

Hi,I wanted to know if there is any possible way to trigger a callback request through setting a conversation attribute ‘last_inbound_call_estate’ to ‘Awaiting callback’. As all I can seem to find is that this data attribute is only accessible through the phone workflow and can only be added and modify by Fin though the workflow.It would be nice if there was an option to set the ‘last_inbound_call_estate’ to ‘Awaiting callback’ for any conversation so the active team members would automatically get the call in their inbox, just like when they request a callback through the phone workflow, but without them having to actively call… Wether it is though API or through a messenger workflow it would be nice to integrate.

Hello,We have successfully integrated your Android SDK (version 15.16.0) into our application. However, we are currently seeing a significant number of crashes reported in Firebase. Unfortunately, we haven’t been able to reproduce the issue on our side so far.Could you please help us investigate this further? Let us know if you need any additional information or logs to assist in the debugging process.Thank you in advance for your support.This is the crash:          Fatal Exception: java.lang.NullPointerException:       at androidx.compose.ui.platform.AndroidComposeView.<init>(AndroidComposeView.android.kt:788)       at androidx.compose.ui.platform.Wrapper_androidKt.setContent(Wrapper.android.kt:77)       at androidx.compose.ui.platform.AbstractComposeView.ensureCompositionCreated(ComposeView.android.kt:258)       at androidx.compose.ui.platform.AbstractComposeView.onAttachedToWindow(ComposeView.android.kt:290)       at android.view.View.dispatchAttachedToWindow(View.java:22479) 

Hi, Is there an Intercom integration with Looker Studio? I’ve seen an older post in which people seemed to run into issues with the API documentation. I wonder if there have been any updates or if there is an easier way now to integrate both. Thanks.

Are there any plans to have macOS SDK in the near future? Specifically I want to use it for embedding the help center inside the app.

Please help. I cannot build a release apk/aab, I’m getting the following error: > Task :app:compileReleaseKotlin FAILEDe: Incompatible classes were found in dependencies. Remove them from the classpath or use '-Xskip-metadata-version-check' to suppress errorse: file:///Users/builder/.gradle/caches/transforms-4/a23eb7edad52ffdf2e2ff09828f4ac13/transformed/jetified-intercom-sdk-base-15.15.1-api.jar!/META-INF/intercom-sdk-base_release.kotlin_moduleModule was compiled with an incompatible version of Kotlin. The binary version of its metadata is 2.1.0, expected version is 1.9.0.Classes that weren't resolved: > com.google.common.util.concurrent.ListenableFuture I’m using the latest version of the library (8.3.0), and my build.gradle is: buildToolsVersion = "35.0.0"minSdkVersion = 23compileSdkVersion = 35targetSdkVersion = 35ndkVersion = "26.1.10909125"kotlinVersion = "1.9.22" 

Hi - We exprience a crash in the latest version of the iOS SDK version 18.6.3 The way to reproduce the crash:1. Open Intercom in the app, start a new chat (or existing one).2. In the conversation choose to add a photo (from library or from camera)3. Before choosing to send - take the internet off (by turning on airplane mode)4. Add the photo5. Tap the ! to try again - but take no action.6. Restore the internet by disable airplane mode7. Wait for Intercom to restore the connection and send the image automatically and after the image is shown as sent (not grayed out) - Tap Try again8. crash!Reproduced 100% of the times. ScreenReco...3-39_1.MP4   

We are facing following issue in our iOS Native app:When the app is closed and the user clicks on the Intercom’s Push Notification, the app opens up but the chat/post opens momentarily and closes. This only happens when the app is closed and notification is clicked, it works fine if the app is in the background/active state.In our case when the app is opened via Push Notification in the app's closed state, main view get refreshed after data fetching.I have done all the Push Notification configuration as per the doc: https://developers.intercom.com/installing-intercom/ios/push-notificationsWe are using iOS SDK Intercom version: 17.1.2 Similar kind of issue was resolved by our Android Team by using Intercom.client().handlePushMessage() . However, such a method does not exist in the iOS Intercom SDK.

Hey there, I’m finding it difficult to understand the rest API docs around file uploads. I would love to have a user fill out a form, and attach an image, and this would be submitted by the API to create a ticket. I see that the “File” type is supported in the tickets, however I’m finding difficulty in figuring out what Intercom wants as a file.  Is there any more documentation that you could point me towards? Or could you provide a quick example of what an image upload would look like with the API?  Thanks, Aaron. 

I'm creating a user in the api and filling in the phone field. I Want fill a field "WhatsApp Number" How I do that?  there is nothing in the documentation

I encountered a problem with opening a chat with a conversation when clicking on a push, when clicking it just opens the application implementation 'io.intercom.android:intercom-sdk:15.11.5' private final IntercomPushClient intercomPushClient = new IntercomPushClient(); @Override public void onMessageReceived(RemoteMessage remoteMessage) { Map<String, String> message = remoteMessage.getData(); if (intercomPushClient.isIntercomPush(message)) { intercomPushClient.handlePush(getApplication(), message); }  @Override protected void onResume() { super.onResume(); checkPendingDeepLink(); Intercom.client().handlePushMessage();  @Override protected void onNewIntent(Intent intent) { super.onNewIntent(intent); setIntent(intent);..... Bundle bundle = getIntent().getExtras(); if (bundle != null) { String link = bundle.getString("link"); if (link != null) {

Hello We're currently facing an issue where CoBrowse sessions are not available in Intercom unless the user is logged in to our site.According to CoBrowse support, the SDK should be initialized as soon as the website loads, regardless of the user's authentication status.They mentioned:“The issue could be that the CoBrowse SDK is only being started when your users log in. Would you be able to check that with your Dev team? I see no reason for it not to be started before the user authentication happens as the agent and user will still be matched through Intercom.”In our implementation, the CoBrowse SDK is initialized for all users, not just those who are logged in.We suspect the issue may be related to how users are matched between Intercom and CoBrowse. When a user logs in, we pass their email to both Intercom and CoBrowse, which seems to enable session matching. However, for guest users (not logged in), no email is available, and as a result, the session is not linked between the platf

How to achieve this? Could someone kindly help or divert me to an article/video I can refer to. Please do help me out, thank you!

Hi there,I've just installed the latest version of the Expo plugin (6.8.1). Everything is mostly working, but there are some issues. I've noticed problems with push notifications, and I'm unsure if they are related to the following:1. We're unable to retrieve the unread message count correctly. The listener isn't working, and even when the app is open, new messages aren't being fetched.2. In chat, replies from an "agent" aren't showing up in real-time. To see new messages, we have to close and reopen the conversation, which disrupts the chat experience.Any advice on these issues would be appreciated.Thank you

Hello,We are currently migrating our react-native app to Expo and we are facing some issues with Intercom push notifications.We are using:"@intercom/intercom-react-native": "8.1.0","expo": "52.0.28",And in app.config.ts, this is our intercom setup:'@intercom/intercom-react-native',{ appId: process.env.EXPO_PUBLIC_SECRETS_INTERCOM_APP_ID, androidApiKey: process.env.EXPO_PUBLIC_SECRETS_INTERCOM_ANDROID_API_KEY, iosApiKey: process.env.EXPO_PUBLIC_SECRETS_INTERCOM_IOS_API_KEY}We have followed the rest of the setup mentioned on github.It seems that the chat works when we open it from the app. The user can send and receive messages as expected.The problem is that the push notifications don’t seem to work at all. We don’t receive any notification when the app is on the background or closed.Could you please advice on what we can check? Thank you,Nikos

Hi, I am currently using the OpenAPI specification provided in your YAML file to generate an API client for the /companies/list endpoint. According to the YAML, pagination is implemented via a "pages" object, which includes a "next" property defined as a starting_after_paging object. This object is expected to contain properties like per_page and starting_after.However, the actual API response returns the "next" property as a plain URL string, for example:"pages": { "type": "pages", "next": "https://api.intercom.io/companies/list?page=2&per_page=1&order=desc", "page": 1, "per_page": 1, "total_pages": 223},"total_count": 223I have verified that this behavior is consistent even when using the API testing tool provided at https://developers.intercom.com/docs/references/rest-api/api.intercom.io/companies/listallcompaniesCould you please clarify whether this is a known issue or an intentional change in the API implementation that has not yet been reflected in the YAML documenta

Hi, I would like to set up a floating banner in our portal between certain time frame and I would like to show it to all users 2 times. how can I do that? I could set it up as ‘’send every time the person matches until dismissed’’  between certain time but I do not want to send more than 2 times

Hey!We are creating tickets for some chats and sending the ticket attributes to an external tool using POST API requests. I’m able to forward all attributes except for any files added to the ticket, as the file attribute isn’t saved like the others.Is there a way to include links to the files in my API call through the Action Builder? I see that the files are stored like this, so I would just need a way to include this in the call. https://downloads.intercomcdn.com/i/o/qwum5ehb/1430332547/0a18547e88a0534a2b11dc66de1c/About+-+Wolt+%28Germany%29.pdf?expires=1742396400&signature=71937dcca587c48f45395961771de4a294247409d94427ef8a309fcc0f603793&req=dSQkFsp9n4RbXvMU3HP0gCfl8Ixw9B04fnL9Av84zX8P2bzVoXE%3D%0A

Actually i am facing a issue and tried a lot of things to solve this bug, but could not find out whats the actuall reason behind this bugIssue:When I click launcher button, widget appears, then the launcher should become back btn to close that widget, but in my case when i first click the launcher widget appears and instead or becoming back btn, launcher suddenly blinks and return to its launcher state,second time  i click the btn, nothing happens, thrid time i click the btn , a new widget appear on top of previous one, at it goes so on.Please help me in solving this issueCode:if session[:user_id]@intercom_hash = OpenSSL::HMAC.hexdigest("sha256", ENV["INTERCOM_SECRET_KEY"].to_s, session[:user_id].to_s)end  <% if ENV['SEGMENT_JS_WRITE_KEY'] %><% if session[:user_id] && !current_user&.admin? && current_user.present? %><% profile = current_user.value&.profile %><script>window.intercomSettings = {api_base: "https://api-iam.intercom.io",app_id

Hey, After migrating from "@intercom/intercom-react-native": "^3.0.5",to latest version "@intercom/intercom-react-native": "^4.0.1",the displaying of specific helpcenter collections does not work anymore.Old code: Does not work after updating the SDKconst res = await Intercom.displayHelpCenterCollections([‘1234567’])// trueNew code: Also does not work with the latest SDKconst collections = await Intercom.fetchHelpCenterCollections();/**[ { "id": "1234567", "title": "FAQ" }]*/const collectionIds = collections.map(_ => _.id);// [ "1234567" ]const collectionContent = IntercomContent.helpCenterCollectionsWithIds(collectionIds);/**{ "type": "HELP_CENTER_COLLECTIONS", "ids": [ "1234567" ]}*/const res = await Intercom.presentContent(collectionContent);// trueThe problem is the same for both methods:displayHelpCenterCollections and presentContent return true, but no Intercom popup is opened.