Popular Topics

 We've had a difficult experience with Fin since the start. We never received any real onboarding or guidance, so we set everything up on our own.Later, our plan turned out to be too small, and we were billed roughly double in overage charges. We tried repeatedly to contact sales to upgrade to a plan that fit our volume, but never got a response.Our company has since decided to move to another provider. For several weeks now we've been trying to cancel, but there's no self-service cancel option, and it seems the only way is for someone at Fin to process it. Our messages through every channel have gone unanswered.We'd really prefer to resolve this directly, but if we can't get a response soon we'll have to consider a consumer protection complaint and legal options.Has anyone dealt with this? Is there a specific contact, form, or process that actually worked for you to cancel?

Connector bug for your reportSymptom: create_article and update_article fail with "This connector requires additional permissions. The user needs to reconnect it from connector settings." Reconnecting doesn't help, because it isn't a real permissions problem. Cause: I bisected it. Any body containing the literal string ${env:<anything>} is rejected, even ${env:MY_SERVICE_TOKEN}. Size, HTML, tables, JSON, ${IPAAS_API_KEY} and ${input:…} all pass on their own, but the full draft stayed rejected until the ${env: string was removed. Why it hit you: it only triggers on content like Cursor's config syntax. Any article documenting that fails, and the error points you at the wrong fix. Workaround I used: writing the placeholder as ${env:IPAAS_API_KEY}. Intercom decodes it, and the read-back showed the stored text as a literal ${env:IPAAS_API_KEY}. I applied the same encoding to the VS Code ${input:…} placeholder as a precaution, without testing it separately. I got past a gateway

Hi,We’re experiencing an issue with the Calendly integration inside the Intercom Messenger on iOS.The Calendly app is installed and configured in our Intercom workspace. The booking flow opens correctly and allows the user to select a date/time and enter their details, but submitting the Calendly form fails.Xcode shows the following error:[Intercom] ERROR - Tried to submit messenger sheet but there was a network error - HTTP Error: 400 bad requestThe same Intercom message and Calendly flow works on Android and proceeds past this step.Environment:Intercom iOS SDK: 19.8.2 Installed via Swift Package Manager (intercom-ios-sp) Flutter app using intercom_flutter Calendly native Intercom integrationWe also updated the Intercom Flutter plugin/native SDK, but the issue persists.Has anyone encountered this with Calendly Messenger Sheets on iOS, or is this a known issue with the current iOS SDK?

In the thread here:The replies state “Try a different network – Firewalls or VPNs sometimes block Intercom,” and, “If you’re on a company network, sometimes firewall or VPN settings can interfere with Intercom loading.”I am dealing with a similar situation for some users on a VPN. I found this list of IP ranges intercom content is hosted from; this could perhaps help individuals with the same problem configure their VPNs: https://static.intercomcdn.com/intercom-ips/us/intercom-ip-ranges.jsonHowever I am not sure this list is comprehensive, as I see other IPs associated with requests to intercom:18.161.6.84 - https://widget.intercom.io3.163.24.116 - https://js.intercomcdn.comIf the intercom team could clarify in their official docs which IP addresses are associated with their service, or offer a static hosting solution, that would be appreciated!

Hi team,We're implementing the require-trusted-types-for 'script'; header in our app and have set up a default Trusted Types policy. However, the Intercom widget script fails on the following line:e.documentElement.innerHTML = t,withUncaught TypeError: Failed to set the 'innerHTML' property on 'Element': This document requires 'TrustedHTML' assignment. Has anyone encountered this issue before? Any suggestions on how to work around it while keeping Trusted Types enforcement?Thanks! 

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 team, We are setting up automatic bug report creation in Jira directly from Intercom using the official Jira for Tickets app with custom automation (Workflows). We would like to achieve this using only Intercom’s built-in tools, without relying on third-party integration services (like Zapier/Make) or a custom backend.Everything works great, except for one thing: screenshots and files attached to the Intercom ticket are not being transferred to the newly created Jira issue.Questions: Is the ability to transfer attachments on the roadmap for the Jira for Tickets app, and is there an estimated timeline for this? Is there currently any workaround using built-in tools (Workflows / Data Connectors) that we might have missed? Thank you!

Hello everyone, I encountered a strange issue while testing user flows for a mobile video editor, similar to the capcut apk tools I've been using. sometimes it takes a long time for the Intercom widget to appear when the app loads larger media files, or it appears after everything else has finished loading.Has anyone else observed that Intercom behaves strangely when handling large files or a lot of ui changes? Is there a better way to queue events to ensure smooth operation, or do you think this is just a performance hiccup? I'd be interested in learning how others have dealt with it.

Hey folks, I was laid off earlier this year. I want to keep my Fin skills current, but I can’t find any information about a free sandbox account. I see there is a 14 day trial, but I’d have to keep setting up a new workspace every two weeks and that doesn’t make much sense as I’d have to recreate everything from scratch. Jobs are asking about my experience with Fin and it’s been months since I used it, so I’m really rusty. I also didn’t get a chance to fully explore the features like workflows at my last job as I was laid off shortly after we moved to Fin. Any suggestions?