Any plans for a Highspot integration?

[britney_zhou]

Hi everyone! 

Our organization uses Highspot for our Go-To-Market documentation and work closely with them. Was wondering if there are any plans for a Highspot integration into Rovo? It would really help with having Rovo as our main GTM AI agent for our CS processes. 

Thanks!

[Rebekka Heilmann _viadee_]

Hi @britney_zhou 

there is a feature request for this integration: [AI-1134] Rovo connector for Highspot - Create and track feature requests for Atlassian products.

As it is still gathering interest, there won't be coming anything anytime soon, I reckon.

You can now feed data into Atlassian's Teamwork Graph yourself, so if you have some techy people and see a high value in the connection, you could build something yourself: Connecting to Teamwork Graph

[Jorge Cammarota]

Indirect Indexing (The Workaround)

1. If your GTM content from Highspot is also hosted or mirrored elsewhere, Rovo can still "see" it. You can leverage existing Rovo connectors if your content is:

• Cross-published to Confluence, Google Drive, or SharePoint.

• Periodically exported (PDFs, PPTs, etc.) to a repository that Rovo already supports.

• Outcome: Highspot remains your management/distribution system, while Rovo acts as the AI query layer by reading the mirrored repository.

2. Custom Integration via API

Since Highspot offers APIs, you could technically build a bridge. This requires development resources but offers a more automated flow:

• The Connector: Build a script that reads content via the Highspot API and syncs it to a Rovo-accessible base (like a dedicated Confluence space).

• Syncing: Use Webhooks or scheduled jobs to ensure the Rovo AI agent isn't giving outdated sales information.

3. Formal Product Requests

Since you want Rovo as your primary GTM AI agent, it is crucial to signal this demand to Atlassian:

• Submit Feedback: Use official channels (Atlassian Support or your Account Manager).

• Engage the Community: Reply to active threads (like the one mentioned with Britney) and provide:

  • Highspot usage volume.

  • Specific CS/GTM use cases.

  • Pain points regarding content duplication.