Popular Topics

I was trying the List collections endpoint under the Help Centre APIs using PaginationTh Pagination Guide describes List APIs as using cursor based pagination, with the “next” parameter containing the “starting_after” parameter which can be used to fetch the next page of resultsHowever, when I tried the List collections endpoint I got this as the result for the “pages” parameter. The “next” parameter gives a URL, not an object as described in the docs"pages": {    "type": "pages",    "next": "https://api.intercom.io/help_center/collections?per_page=1&page=2",    "page": 1,    "per_page": 1,    "total_pages": 4  }Here are the headers I used for reference:{“Authorization”: “Bearer <token>“,“Accept”: “application/json”,“Intercom-Version” : “2.13”}Since I’m passing the intercom-version I don’t expect this to be an error with the version. Please explain the correct way to use PaginationI see a related issue here. However I’m unsatisfied with the solution provided. In case the API

I’m trying to bring down the number of duplicate emails in Intercom so I can actually use the Hubspot integration. It looks like one of the culprits is the Stripe integration. Many of my duplicates look like this: User 1:email = jane@doe.com user_id = foobar stripe ID = unknownUser 2:email = jane@doe.com user_id = unknown Stripe ID  = abcdefI can manually go through and archive these junk users that Stripe has created, but then my question is:Can I prevent Stripe from doing that in the first place? Can it just wait for the “good” user (one with a user_id) and attach the stripe data to that one? If I archive the stripe-connected user, will Stripe attempt to find and resync with the good user?

I tried to add intercom help center articles as an embed iframe on React. But it's rejected because of CORS issue. Can you add our website, so that we can avoid CORS issue? Or is there any work around?

I’m using the API to create and manage tickets, and seeing some unexpected things in the auto-email-notification subject lines.The steps I’m following:Create a ticket via the API. Type: Tracker Ticket. It properly appears with my title and description. (Notifications skipped). Assign that ticket via the API. (Notifications skipped). Add a comment to the ticket via the API. For this step I’m not setting skip_notifications to true, so a notification does get dispatched.The problem is that the subject line of that notification is: Re: [Company Name] [Assignee Name]: ''The empty single quotes indicate that it should be possible to get something to appear there. I’d love to be able to display the ticket title, or the contents of the comment that caused the notification, or pretty much anything other than ‘’.

Here are the errors:  jetified-intercom-sdk-base-15.10.3-runtime.jar: D8: java.lang.NullPointerException: Cannot invoke "String.length()" because "<parameter1>" is nullWhat I’ve Tried: Checked build.gradle for SDK version compatibility Cleaned and rebuilt project (./gradlew clean && ./gradlew build) Searched through Intercom docs and changelogs Looked at open issues in the GitHub repo My Setup: React Native version: 072 Intercom SDK version: 15.10.3   Gradle: 8.0.1 Questions: Are these methods deprecated or moved to a different namespace? Is there a recommended way to check login state and fetch user attributes in the latest SDK? Should I downgrade to a previous version of the Intercom SDK? Any help is greatly appreciated!

*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'*** First throw call stack:(0   CoreFoundation                      0x00000001804ae0f8 __exceptionPreprocess + 1721   libobjc.A.dylib                     0x0000000180087db4 objc_exception_throw + 562   CoreFoundation                      0x0000000180393044 -[__NSArrayM insertObject:atIndex:] + 12523   Intercom                            0x00000001060eb528 IntercomSDK_saveViewHierarchy + 4969884   Intercom                            0x00000001060eadec IntercomSDK_saveViewHierarchy + 4951365   Foundation                          0x0000000180d54084 -[NSObject(NSKeyValueCoding) setValuesForKeysWithDictionary:] + 1846   Intercom                            0x00000001060eacd4 IntercomSDK_saveViewHierarchy + 4948567   Intercom                            0x00000001060eac78 IntercomSDK_saveViewHierarchy + 4947648   Intercom                           

We are encountering crashes on Android devices related to Intercom SDK version 15.9.1. Stack Trace:Failed to build unique file: /storage/emulated/0/DCIM/vr-unit.gif bucket_display_name=DCIM volume_name=external_primary date_modified=null date_expires=null _display_name=vr-unit.gif mime_type=image/gif _data=/storage/emulated/0/DCIM/vr-unit.gif _size=null is_trashed=0 is_pending=0 bucket_id=-2075821635 relative_path=DCIM/ android.content.ContentResolver.update (ContentResolver.java:2318)arrow_rightio.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.saveImageOnApi29Above (PreviewViewModel.kt:201)io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel.access$saveImageOnApi29Above (PreviewViewModel.kt:35)io.intercom.android.sdk.ui.preview.viewmodel.PreviewViewModel$saveImage$1.invokeSuspend (PreviewViewModel.kt:92)kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith (ContinuationImpl.kt:33) Device : Mostly Google PixelAndroid Version: 11, 12

Hi,  So I’ve been working on setting up my account and I’m stuck at this for over a week now.  I’ve got a lead form and these leads are being sent to Intercom, with custom lead data (attributes) such as event date and event type. This is all sent through zapier and Intercom API.  However, when a lead already exists, it’s not updating the lead with these custom attributes. All API work, I get the right 200 response, I do not get duplicated leads and so on. Mapping is all correct and we tested via Postman and via Intercom test enviroment, here it all works, yet sending real data via Zapier to Intercom does not update the lead.  We’ve checked with both support teams and lead data is sending through zapier to Intercom. However Intercom support mentioned they do not receive the body call, while the zapier logs show this is being sent correctly.  What is going wrong here, is this just a bug? I can’t believe no one is using the API on zapier to update lead profiles. I’ve spent 10 hours + ever

Hi Intercom team,I’m Romain from Ringover, a partner working with clients on Intercom integrations. I’d like to submit a feature request regarding the ability to ⭐ update internal notes ⭐ via your API.Currently, instead of updating the original internal note with new content (e.g. an AI-generated call summary), the API creates multiple separate notes for each update. Since Ringover also sends additional after-call events such as updated notes and tags, this results in a cluttered view within the Intercom workspace.Being able to update an existing note via API would significantly improve clarity and user experience for our shared clients.Could you please forward this request to the product team?Thank you for your collaboration.Best regards,Romain 

Hi Team,Is there a way / specific webhook one could use to subscribe to events when a Linear ticket is created from an Intercom conversation? I was unable to identify any specific one - as far as I can tell the only way to check from Intercom side is to loop through the conversation parts looking for the note signifying the connection.Thank you in advance!

It appears that the only opportunities for aggregation are Average, Median, Minimum, and Maximum but I want a Sum of all the time spent handling tickets for the last three months. How can I aggregate by Sum instead? How can I either remove the aggregation options so I can see a total sum, or get a full list of all the conversations and all of their handling time so I can sum it myself? Thanks!

Noticed an issue with the conversation search API, specifically on boolean fields when coupled with the != operator.For example the below query (even when run from the “Try it” button on the docs page) returns the same exact response as when using the = operator.  POST https://api.intercom.io/conversations/searchBody: {    "query": {        "operator": "AND",        "value": [{      "field": "read",      "operator": "!=",      "value": "true"    }]  }}I tested with different value types (string, boolean), other boolean fields (ex: open), as well as with “false” values. The behavior is the same.Please assist.

Hello everyone, I have been receiving this error when the app initialize on the mobile. @intercom/intercom-react-native is at 8.5.0, which seems to be the latest. iOS version is at 17.2   

Dear Team,I’m Prakash Hinduja from Switzerland, I'm a Consultant and Advisor, I’m exploring ways to sync my website with my social media accounts to streamline content sharing and enhance engagement. As part of this initiative, I would appreciate your suggestions on the most effective methods or tools you’ve used or come across. RegardsPrakash Hinduja Switzerland 

Release Date: 11-06-2025 🐛 Bug Fixes Fixes a bug where articles could render in the incorrect interface style.

Hello,When I query the conversation_tag_history table, I noticed there can be multiple conversation_updated_at values for the same tag_id and conversation_id.Usually the MIN(conversation_updated_at) value is accurate, but I wonder how this can be the case?It happens frequently so I don’t think it’s because someone is removing a tag and adding it again, but I can be mistaken.Thanks in advance!

Hello All,As I continue scaling tiered support, I’m working to improve how we monitor both real-time and historical trends. Specifically, I’m trying to track: Time from conversation start to first assignment (Time in Unassigned) Time from first assignment to reassignment (Time in Tier 1) Time from reassignment to first close (Time in Tier 2) I also want to make sure we’re capturing the entire lifespan of the ticket, including both open and snoozed time.Right now, inbox views are the only way to surface aging tickets—but they aren’t designed for this kind of analysis. They don’t function like reports, and they don’t allow us to layer in the conversation attributes we’ve added, such as product area or difficulty level.That makes it tough to proactively support aging tickets, coach the team in real time, or dig into specific themes during 1:1s—especially when trying to identify which product areas need more targeted coaching.I’d love any ideas on how we can bring better visibility to

Hello everyone; When the iOS app launches, we log in our Intercom user as an undefined user. Later, when the user log in or creates an account with a JWT token and we login them in as an identified user through Intercom, we can't see the undefined user's messages. When we try to send a message, we get an error. I did the SDK integration correctly and the JWT token is working properly. But it's not automatically merging users' messages. How can I solve this problem? SDK Version; 18.8.0iOS: 18.4, 18.5UI Error;Something’s gone wrongCouldn’t load the conversation Intercom Request Error;Path: https://<app-id>-ios.mobile-messenger.intercom.com/messenger/mobile/conversations/215469369303322Code: 404{ "type": "error.list", "request_id": "004gb7n4n158kmpf4qeg", "errors": [ { "code": "not_found", "message": "Resource Not Found" } ]}  ​

We have a webhook subscription setup for our app that is set to trigger for the event conversation.rating.added. An app user is having issues as it’s only triggering for a bot admin that they’ve setup. When other folks on their team receive a rating, those do not trigger a webhook. Is this the expected outcome? The authenticated user has admin permissions, the assumption was that they’d have visibility over the entire organization. 

Hello, we've recently updated our SDK to the latest version (16.0.0) and we've been seeing a few crashes in production related to the in app notification. This seems to happen when showing the Full notification, as there seems to be something missing in the layout that intercom uses internally. We've just bumped to the latest version, but looking at the code, that doesn't seem to solve this particular issue.This is the stack trace we're getting:Fatal Exception: java.lang.NullPointerExceptionParameter specified as non-null is null: method io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.addInappNotificationCardToView, parameter composeViewio.intercom.android.sdk.m5.notification.InAppNotificationCardKt.addInappNotificationCardToView (InAppNotificationCard.kt:3)io.intercom.android.sdk.overlay.ChatNotification.populateViewsWithData (ChatNotification.java:90)io.intercom.android.sdk.overlay.ChatNotification.display (ChatNotification.java:64)io.intercom.android.sdk.overlay.InAp

Hey! We have started getting this crash recently and switching to the latest sdk(16.1.0) didnt help. Can you please help me with this? Thanks! Missing keys: [timestamp] in '{teammate} flyttet saken til {status} {timestamp}'Full crash log: java.lang.IllegalArgumentException: Missing keys: [timestamp] in '{teammate} flyttet saken til {status} {timestamp}' at io.intercom.android.sdk.utilities.Phrase.format(Phrase.java:0) at io.intercom.android.sdk.utilities.Phrase.format(Phrase.java:189) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.TicketInAppNotificationContent(InAppNotificationCard.kt:180) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt.InAppNotificationCard(InAppNotificationCard.kt:124) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.invoke(InAppNotificationCard.kt:75) at io.intercom.android.sdk.m5.notification.InAppNotificationCardKt$addInappNotificationCardToView$1$1$1.i

I'm currently integrating Intercom into my React Native Android Expo app and running into some build issues that I haven't been able to resolve. I’ve followed the official setup guide and installed @intercom/intercom-react-native, but the build fails when running the Android version of the app.Details:React Native version: 0.74.5   Intercom SDK version: @intercom/intercom-react-native@8.3.0"   Java version: Java 17 on M1 Mac   Error message: TypeError: null is not an object (evaluating 'IntercomEventEmitter.UNREAD_COUNT_CHANGE_NOTIFICATION')

Hola comunidad,Estoy integrando Intercom en una app React Native (bare, usando EAS Build, no Expo Go) y tengo el siguiente problema:Uso el método Intercom.getUnreadConversationCount() para mostrar un badge de mensajes no leídos.El usuario está correctamente identificado (userId y email coinciden con los del panel web).Desde el panel web de Intercom, envío mensajes al usuario (tanto desde un agente humano como desde el bot).En el panel web, los mensajes aparecen como “Not seen” para el usuario.Sin embargo, en la app, el método getUnreadConversationCount() siempre retorna 0, incluso después de recibir mensajes nuevos y refrescar el conteo.Ya probé con mensajes automáticos/bot y tampoco se refleja el conteo.No necesito push notifications, solo quiero mostrar el número de mensajes no leídos.Estoy usando la última versión de @intercom/intercom-react-native y la integración nativa está bien (la mensajería funciona).¿Alguien ha tenido este problema?¿Hay alguna limitación conocida en el SDK de

We're experiencing an issue where the mobile carousel feature gets dismissed automatically on app start for logged-in users. Our app is built with React Native and Expo.To isolate the issue, we tested with a minimal project containing only an empty screen and Intercom login. The issue does not occur on the first app launch (since Intercom login hasn't been triggered yet). However, once the user is logged in and we send a carousel from Intercom, reopening the app causes the carousel to briefly appear before getting dismissed.We also ensured that Intercom login is only called on the first launch, as a support ticket suggested that calling it repeatedly might be causing the issue. Despite this, the problem persists. Additionally, we've attached a video demonstrating the issue: The splash screen appears first The carousel appears briefly The carousel gets dismissed Our white screen is displayed Similar issue is mentioned in  

Hi Intercom We are trying to update the Intercom SDK for our app to the latest version, currently still on version 2.0.1 We are using React Native with Expo (version 51.0.39), and it works fine with version 2.0.1 (we are using the Expo plugin from version 8 of the React Native package), but if we try to update to the latest version, we get strange behaviors on iOS:For some users, during testing, some buttons are missing (for example the “close” button on the top left is missing, you can actually touch it but the icon is missing) Can’t send messages Can’t upload files from Google Drive   Other users had a black screen that went away after restarting the app (all of these tests were made with a release build deployed to TestFlight for iOS and Play Store as closed beta) This issue is not happening on all devices and not for all users (we had issues on iPhone 11 Pro with iOS 18.3.1, but was working fine on an iPhone 16 Pro with iOS 18.2.0)This is how we have configured the Explo plugin:[