I'm trying to build a company-wide internal support agent that has access to all of our company resources. Does anyone else find Atlassian to be very restrictive when trying to add a Custom Website connector?
For context, we also use Intercom Fin AI for customer-facing support, and with Fin AI, I've had no problem adding a variety of custom websites to our Intercom AI index. With Atlassian though, all of the custom websites that I need to add can't be added due to this error:
"Can't access your site
We're having trouble connecting to your site. Check the details, or see our docs for other suggestions."
Specifically I'm having the issue with all of these public resources:
- support.wunderite.com - Intercom knowledgebase - this one get's successfully added, but it's clear that it's not being indexed. If I try to add the Intercom domain version of our knowledgebase, it's blocked. This is a huge blocker for us because we have no way to update Intercom's robots.txt and our knowledgebase is one of our most useful resources. A direct integration with Intercom would be great and maybe resolve this issue.
- docs.wunderite.com - internal API docs - we should be able to update our robots.txt to explicitly allow atlassian-bot
- releases.wunderite.com - release notes via Released.so. I met with the CEO yesterday and he said he'll look into updating their permissions. Released.so does have an integration with Confluence, so as a workaround, I could at least sync our release notes to Confluence.
As far as I can tell, none of these sites are explicitly blocking AI agents, but they also don't explicitly allow atlassian-bot. It seems like Atlassian is far more restrictive than other agents I've used, so I'm not able to add critical knowledge sources. Has anyone else encountered this or know how to address it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.