Popular Topics

I’m working on an email reply automation tool using the Intercom REST API. I’m trying to retrieve the email history — the quoted text that appears collapsed behind the three dots (“…”) when a customer replies to an outbound email we’ve sent them. Three dots for expanding email historyFrom inspecting the network traffic, I can see that this data is retrieved via a private Ember API endpoint:curl 'https://app.intercom.com/ember/inbox/email_history?metadata_id=XXXXXXXXX&app_id=yyyyyyy Is there an equivalent method in the public REST API to access this email history or quoted content?I’ve already tried GET /conversations/{conversation_id}, but the response only includes the conversation parts - it doesn’t contain the quoted email thread (the hidden “three dots” section) in either the parts or metadata.To clarify, customers are replying directly to our outbound emails (sent via our own system, not through Intercom). When we fetch the resulting conversations through the API, we can see t

Hello everyone,I am facing an issue with Intercom Push Notification when it is a cold start (App is terminated, you receive a Push Notification and this notification will wake the App). While testing on Simulator that, if i am running my app from Xcode, terminate the App (on Simulator, not on Xcode), send a message to my test user, wait the push notification, receive it, tap on it but when i tap on it, Intercom Messenger does not opens the modal chat, it keeps me on my WorkListView (WorkList is a subview of RootView, that appears after SplashViews finish animation and transit to WorkListView).I have already made installation (API Key, API ID and Push Notifications are enabled on Settings > Channel > Messenger > Install > Install for Mobiles), Apple Developer is already configured, when i open the Messenger on my App, i can send and receive messages. When App is open but in background i am able to receive and wake the app in the correct modal Intercom window chat, but only t

 Hey community,Trying to connect Intercom to our Discord server and hitting this error:"This bot can't join more servers as it has not been verified or is requesting gateway intents it has not been verified for."Fin confirmed the bot is pending Discord verification and there's no workaround. Raised it with Engineering Support, they confirmed it's a known bug, created a ticket, no ETA.A few questions:Is anyone successfully using the Discord integration right now? Was there a point where it worked and stopped, or has it never worked? Any workaround — e.g. does the server need to be a verified/community Discord server?Seems like a critical gap given Intercom is promoting it as a supported channel. Curious if others are affected.

Bug Report: Unrecognized selector sent to CPTemplateApplicationScene (CarPlay) — iOS 27 Summary The Intercom iOS SDK crashes the host app with an **unrecognized selector** exception when aCarPlay scene is involved in scene lifecycle. Intercom sends a `UIWindowScene`-only selector to`CPTemplateApplicationScene`, which is a sibling of `UIWindowScene`, not a subclass — so themessage is unhandled and the app terminates. This is the same long-standing defect previously reported as`-[CPTemplateApplicationScene windows]: unrecognized selector`( and )On **iOS 27** the selector has changed to a different `UIWindowScene`-only API: -[CPTemplateApplicationScene _enhancedWindowingEnabled]: unrecognized selector sent to instance Environment Intercom SDK | 19.3.2 (intercom-ios-sp, SPM). Also reproduces on latest 19.6.3 — updating does not fix it.iOS 27 (also historically reproduced on earlier iOS with the `windows` selector variant)SwiftUI/UIKit app with a separate CarPlay scene (`CPTemplateApplicati

I work for a company that rents out vehicles. We've introduced a user attribute that displays the license plate of the vehicle that is being reserved. As soon as a user reserves a different vehicle, this attribute changes into a different license plate.  I want to be able to instantly start a chat, or send a message, as soon as this attribute changes. During our tests we were only able to send chats and posts when a user matches the rules at the start of their session when they launch our app, but not after that. Does anybody have any idea on how to send chats, post, carrousels etc. after the initial launch of our mobile app?

Release Date: 01-07-2026 🐛 Bug Fixes Fixed a crash that could occur at launch on some iOS Simulator runtimes.

The Intercom platform has following webhook topics: - conversation.admin.replied -- Admin conversation replies - conversation.operator.replied --  Fin/Bot replies to a conversationHere all topics https://developers.intercom.com/docs/references/webhooks/webhook-modelsDuring the tests with reusable workflow, I noticed that Bot replied are send in both topic. As a result, service receive two messages.Below an example of Bot reply message in `conversation.admin.replied`:{ "type": "notification_event", "app_id": "l4e36xhv", "data": { "type": "notification_event_data", "item": { "id": "215474343849634", "...": "...", "conversation_rating": null, "title": "Andrew", "custom_attributes": {}, "conversation_parts": { "type": "conversation_part.list", "conversation_parts": [ { "type": "conversation_part", "id": "4576

Release Date: 09-06-2026 🚀 Enhancements Added security enhancements. 🐛 Bug Fixes Fixed a crash that could occur during app launch.

Clari and Salesloft announced the gradual sunset of Drift in March 2026. No hard end-of-life date, no confirmed migration runway. If you're waiting for a firm deadline before you act, that deadline may arrive with less lead time than your data volume requires.This is what to prioritize before your access disappears.The data that's hardest to recover once it's goneNot everything in Drift carries equal weight. Contacts and lead records are relatively portable — CSV exports handle most of it. What's harder to reconstruct is conversation history: transcripts, timestamps, assignees, thread structure, tags, and the metadata that makes historical conversations searchable and useful.Drift enforces a 600 requests/minute API rate limit. That's the hard ceiling on extraction speed regardless of which method you use. If conversation transcripts matter to your team — for training, compliance, context, or handoffs — budget 2–3 weeks for the extraction alone. That's not a migration timeline. That's j

Hey everyone - just shipped TicketReel, a Canvas Kit app I built for the Intercom inbox.The idea: when an agent resolves a ticket, they add an internal note with the resolution steps, then click Generate Video in the TicketReel panel. The app turns that note into a 60-second branded AI avatar video — scripted by GPT-4o, rendered via HeyGen, captioned via Whisper — and posts the video link back to the conversation as an internal note.The video can be shared with the customer or published to your knowledge base, so the same resolution helps future customers who hit the same issue.Built with Canvas Kit + the Conversations API. Happy to answer any questions about how it works under the hood.App Store listing:https://ticketreel.chriscastle.com/   

Hi Intercom Team,We're hitting intermittent errors from the REST API that appear out of the blue — not correlated with our request rate or any code change on our side — and that succeed when we retry a short while later.The responses come back as HTML (nginx), not the usual JSON. Two examples:404 Not Found — GET /companies/scroll, x-request-id: 000fb95rqvhcl5nf9to0 403 Forbidden — seen previously (HTML, no x-request-id / x-ratelimit-limit headers)We've increased our retry/backoff, which recovers most occurrences, but some still fail outright.This looks like prior reports:https://community.intercom.com/api-webhooks-23/getting-404-502-and-504-error-from-api-at-the-first-time-then-success-after-retry-10039 https://community.intercom.com/api-webhooks-23/api-requests-are-returning-403-4656Any help here would be pretty appreciated. Happy to share timestamps and more request IDs.Thanks,Faruq 

If you're still on Drift, you've probably heard: Clari + Salesloft announced the gradual sunset of Drift in March 2026, with no hard end-of-life date confirmed. A vague timeline isn't a safety net — it's a risk. Post-acquisition, releases slowed, CSM support was eliminated for most accounts, and a 2025 data breach took the platform offline for ten days with limited communication. That's what you're migrating away from.  Why Intercom?The use case overlap is real. Intercom has evolved into a full AI-first platform that combines live chat, ticketing, and Fin AI in a unified workspace — so if your Drift setup handled both inbound leads and post-sale support, Intercom handles both natively.A few things that matter when you're comparing:Pricing: Drift's minimum entry was $2,500/month. Intercom's Essential plan starts at $29/seat/month and includes a shared inbox, Fin AI, and a help center. Integrations: Intercom offers 400+ integrations across support, analytics, and marketing. Drift's deepe

We’re migrating from Zendesk to Intercom.In our App, we have notes that preserve certain actions and any associated Zendesk tickets with URLs to that ticket, like https://{workspace}.zendesk.com/agent/tickets/12345.We’d like to record a direct URL to a ticket in the same fashion with Intercom. However, it’s not immediately apparent what that URL would look like.If I have just created an Intercom ticket via the API with id 12345, what would the URL to that ticket look like?

Hi there.Intercom chat does not load on Safari Mobile (iPhone). The window.Intercom object is not available, and the chat widget does not appear. However, the same implementation works correctly on: Chrome (desktop and mobile) Safari on macOS desktop Expected behavior Intercom should initialize and expose window.Intercom, and the chat widget should be available on all supported browsers, including iOS Safari. Intercom is integrated via GTM and it’s initialized in a React hook: Library: react-gtm-module

Hi,I’m using the Intercom Messenger SDK in a React application and I’m trying to pass contextual data onto the conversation as conversation attributes.For example, I want to set values such as:workspace_name workspace_id current_url subscription_plan item_id item_title item_urlThese values are specific to the conversation the user is starting, as a user may be in different workspaces or different parts of the application at different times, so storing this as user attributes is not appropriate because the values can change from conversation to conversation.Fin suggested updating user attributes via the SDK, but that does not solve the problem for us. We need the data attached to the conversation itself, so it can be used reliably in Workflows, Inbox, and downstream connectors.It feels like the Messenger SDK should support setting conversation attributes when opening or creating a conversation. I’d prefer not to make a separate REST API call to update the conversation after it has been

Scribe tutorial videos are very helpful for customers.  We would like to embed in Intercom using iframe.  Is this something product is considering, or may have already implemented?

Hey everyone,Small finding I wanted to share for those of you who prefer a cleaner workspace.A common complaint is that Intercom is browser-only, but there's a neat trick to make it feel like a proper desktop app, at least visually. No extra software needed. Here's how:Press Windows + R, type the following, and hit Enter: chrome --app=https://app.intercom.comIn the code snippet above and in the following snippets below, the command is shown as chrome -, but it should be chrome - - (double dash). However, the markdown editor converts this to just one dash. If you simply copy the commands everywhere, it will always be correct!This opens Intercom in a stripped-down Chrome window: no tabs, no address bar, no browser toolbar. It sits in your taskbar like any other app and feels much more focused.To be clear: this doesn't improve performance, loading times, or anything under the hood. It's purely a visual/UX improvement for those who like a dedicated window without browser distractions.Inter

I noticed a regression in conversation webhooks. The regression effects messages with embedded images.Previously, in version of API 2.14 , embedded image in a message (e.g. paste screenshot from clipboard) was send as in webhook as an embeedded `IMG` in conversation part’s body. After releasing 2.15, the behaivor of v2.14 also has changed. The embedded image(-s) are available both in `body` and `attachments`. As a result, users receive a duplicated images in replies. Is there a way to restore the previous behaivour for v2.14 and not include an embedded images in `attachments`? Example of conversation part from webhook payload (v.2.14):{ "type": "conversation_part", "id": "45209530418", "part_type": "assignment", "body": "<p class=\"no-margin\">Image test<br>​</p>\n<div class=\"intercom-container\"><img src=\"https://downloads.intercomcdn.com/i/o/l4e36xhv/2373221822/cdc43c786608e690132109617c4e/image.png?expires=1778501700&signature=2421a4a292d391e9aeb

For those of you managing multiple brands within Intercom, I'd love to hear about your approach and any lessons learned.What best practices have worked well for you when using Intercom and Fin across multiple brands? Are there specific do's and don'ts you would recommend?Intercom appears to be optimized primarily for single-brand organizations, so I'm interested in learning how others have structured their instance, content, workflows, and AI experiences to support a multi-brand environment.  As an Intercom Manager, my focus is on managing the customer experience, support operations, content, and AI performance—not on building and maintaining complex technical integrations or data connector strategies. We have dedicated teams for that. I'm particularly interested in understanding how other organizations have kept multi-brand management simple, scalable, and sustainable from an operational perspective.What has been most successful for your team? And just as importantly, what mistakes or

I was wondering if there’s a timeline or expected timeframe at least to when can we expect intercom’s MCP to expand outside the US hosted servers? 

Hey Team, Quick question: “Is it possible to create an alert via Workflows or some other means to alert via Slack when a customer rates a conversation with a teammate as poor?” e.g. CSAT Score is 3 or less.Intercom has the ability to alert Slack Channels based on other workflow triggers like no response within X minutes or an unresponsive conversation, but for us to be able to manage DSATs as they happen with a live alert via Slack or some other modality would be super beneficial to our Support Managers and leaders to help coach and improve our teams. Please let me know if any of you have any ideas on how we can institute something like this or build something like this using Intercom and Slack. Thanks again! 

Hi,I have embedded the Intercom script using Javascript. When I checked the Intercom setting configuration, everything looked good to me. But when I tried to init Intercom messager, I got an error "Invalid user_hash". Then I tried to check the user_hash value in the setting and compare it to the value in the dashboard. It's all the SAME. Why I still got this error?  

We’re trying to export Intercom data to Google BigQuery to run more advanced analytics. Right now, we can only view basic reports in Intercom, but we want to analyze conversation trends, response times, and customer behavior alongside other data in BigQuery.Ideally, we need a way to:Regularly sync Intercom conversations, user attributes, and events into BigQuery. Structure the data properly so it’s easy to query. Avoid manual exports and keep everything automated. What’s the best approach to get this data into BigQuery?

Title: How to get our redirect URI allowlisted for MCP DCR?Body:Hi team,We're integrating Intercom's MCP server into our platform, which lets customers connect their own Intercom accounts to AI agents they build with us. When attempting Dynamic Client Registration, we get:POST https://mcp.intercom.com/register{ "error": "invalid_redirect_uri", "error_description": "Redirect URI https://app.integry.io/auth/redirect/ is not in the allowlist, reach out to Intercom Customer Support if you believe we should support it"}A few questions:What's the process to request a production redirect URI be added to the allowlist? Is this handled through Customer Support, developer hub, or a partner channel? Are there review criteria or a security questionnaire we should prepare for? Can we allowlist a staging URI alongside production in the same request? As an alternative — does the MCP server accept access tokens issued by a standard Intercom OAuth app (via app.intercom.com/oauth) as bearer tokens? If

Hi everyone,since around April 17th, our Shopify Storefront MCP Data Connector ("Search shop catalog") has been completely broken. Every call returns:"Tool not found: search_shop_catalog"Background:Shopify renamed the Storefront MCP tool from search_shop_catalog to search_catalog as part of their UCP migration. The old tool is being deprecated (deadline June 15, 2026), but on some stores it has already been disabled — including ours.What I tried:1. Followed Intercom Support's recommendation: deleted the tool and re-added it. Intercom now correctly detects the new search_catalog. ✅2. But when calling it, I get a different error:"Invalid arguments: The property '#/meta' of type string did not match the following type: object [...] '#/catalog' of type string did not match the following type: object"This means: Shopify's new UCP-compliant tool expects meta and catalog as JSON objects, but Intercom serializes them as JSON strings. The result is rejected by schema validation.I tested the sam