Highspot

Name of app / service

Highspot

Link to developer documentation

[Highspot REST API documentation] https://developer.highspot.com/docs/rest-api

Highspot also offers an [MCP Server for external AI agents](https://www.highspot.com/product/mcp-server/), which may be particularly relevant to this use case. Highspot states that its MCP tools support searching content, retrieving specific items, and recommending content based on contextual questions.

Is lack of support preventing you from moving forward, or do you have a workaround?

Yes. Lack of a supported Highspot connection prevents us from delivering the intended experience within Jenius.

The temporary workaround is for users to search Highspot separately and manually provide Jenius with the relevant content or links. This interrupts the workflow and prevents Jenius from finding and recommending approved content when requested.

Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!

Our initial requirement is read-only, on-demand access to Highspot content. We would like the following actions:

Search Highspot content using a natural-language query or keywords.
Return matching content with its title, description, content type, metadata, and Highspot URL.
Retrieve the details and, where permitted, the contents of a selected item.
Recommend relevant Highspot content based on context supplied by Jenius, such as a customer, opportunity, industry, sales stage, or user request.
Respect the permissions of the authenticated Highspot user so that Jenius only returns content the user is authorized to access.

Highspot should only be queried when a Jenius Tool, Play, or user instruction explicitly requests it. We do not want every Jenius conversation to search Highspot automatically.

No triggers are required for the initial use case. Future requirements may include detecting newly published or updated content, but the immediate priority is on-demand content search, retrieval, and recommendation.

No source file or test is named. Start with the Highspot REST API documentation and review the existing Pipedream integration patterns for authenticated API actions. Done means providing on-demand search, retrieval, and recommendation capabilities while respecting the authenticated user's permissions and avoiding automatic searches.

Written by the indexing model from the issue text.