> For the complete documentation index, see [llms.txt](https://docs.slapfive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slapfive.com/integrations/highspot/map-slapfive-to-highspot.md).

# Map SlapFive to Highspot

### 1**. Identify Highspot Spots**

You can post SlapFive Boards and Stories to one or more Spots in Highspot. Indicate the Spot Name, the Spot ID, and the rules for which types of Boards and Stories should go into each Spot. The same Board or Story can go into multiple Spots.

<table><thead><tr><th width="170">Spot Name</th><th width="158">Spot ID</th><th>Which types of Boards and Stories go to this Spot?</th></tr></thead><tbody><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>

### **2. Identify Highspot Lists**

You can post SlapFive Boards and Stories to one or more Lists in Highspot. Indicate the List Name, the List ID, and the rules for which types of Boards and Stories should go into each List? The same Board or Story can go into multiple Lists.

<table><thead><tr><th width="170">List Name</th><th width="158">List ID</th><th>Which types of Boards and Stories go to this List?</th></tr></thead><tbody><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td></tr></tbody></table>

### **3. Specify field mappings**

This table shows the Highspot fields that get populated, with the associated SlapFive field or value:

<table><thead><tr><th width="207.22555010549974">Highspot Field</th><th width="295.69011128578046">SlapFive field, source or value</th><th align="center">Required?</th></tr></thead><tbody><tr><td>Spot</td><td><em>24-character ID of the Spot</em></td><td align="center">Yes</td></tr><tr><td>Type</td><td><em>web_link</em></td><td align="center">Yes</td></tr><tr><td>URL</td><td>Board URL or Story URL</td><td align="center">Yes</td></tr><tr><td>Title</td><td>Board Name or Story Label</td><td align="center">No</td></tr><tr><td>Description</td><td>Board Headline or Story Summary</td><td align="center">No</td></tr><tr><td>Author</td><td>A person to attribute the content to</td><td align="center">No</td></tr><tr><td>Date Created</td><td>Date of posting to Highspot</td><td align="center">No</td></tr><tr><td>Internal</td><td><em>False</em></td><td align="center">No</td></tr><tr><td>Link Embed Code</td><td>&#x3C;iframe 'SlapFive_URL' frameborder='0'>&#x3C;/iframe></td><td align="center">No</td></tr><tr><td>CMS: ID</td><td>Board ID or Story ID</td><td align="center">No</td></tr><tr><td>CMS: Integration</td><td><em>SlapFive</em></td><td align="center">No</td></tr></tbody></table>

### **4. Flag the Boards and Stories**

You can decide which SlapFive Boards and Stories should post to Highspot. To do this:

1. If you plan to send Boards to Highspot, in SlapFive Settings, create a Dynamic Field for the Board object called *Show in Highspot.* Make it a YES/NO field.
2. If you plan to send Stories to Highspot, repeat step 1 for the Stories object.
3. For all Boards and/or Stories you want to send to Highspot, edit the Board or Story, set the  **Show in Highspot** field to *Yes*, and **Save** the Board or Story.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.slapfive.com/integrations/highspot/map-slapfive-to-highspot.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.