LogoLogo
  • Introduction to the Ebbot Platform
  • Ebbot Platform
  • Bot basics
    • Scenarios
    • Entities
    • Triggers
    • Training center
  • Scenarios
    • Cards and syntax
      • File Input
      • Text card
      • Input
      • Buttons
      • Image
      • File
      • Carousel
      • Location
      • List
      • Contact Agent
      • Rating request
      • Custom component
      • CoBrowsing
    • Transition
    • Card properties
  • AI Insights
    • Setup and Configuration
    • Using the Insights Dashboard
  • EbbotGPT
    • Knowledge
      • Data source transformer
      • Source types
        • File
        • Website scrape
        • Docx file
        • TOPdesk API
        • Sitevision API
        • SharePoint API
          • Create app with Sites.FullControl.All permission in Azure
          • Ebbot SharePoint Postman Guide
        • Confluence API
    • Configurations
    • Persona
    • GPT Evaluation
    • Embedder models
    • EGPT models
  • Custom vocabulary
  • Tutorials
    • Create your first scenario
      • Select a trigger
      • Add bot responses
  • Data Object
  • Release notes
  • For developers
    • Ebbot SDK
    • Safe Exchange API / Vault
    • Subdomain manager
  • EbbotGPT API
  • Chatbot & Live chat
    • Install chat widget
    • Chats API
    • Chat widget API
    • Datasource API
    • Sales tracking for live chat
    • Webhook
      • Incoming webhooks
      • Outgoing webhooks
    • SMS API
      • Authentication
      • Send SMS
      • Errors
      • Encoding
    • Python components
    • Intent detection (NLP)
  • Product guides
    • Product data feeds
    • Install guide
    • Product guide events
      • Product guide user events
      • Received events
      • Send events
    • API & webhooks
    • GA4 integration
    • Klaviyo integration
  • Messenger marketing
    • Install popup
    • API & webhooks
  • For chat agents
    • Ebbot Chat
      • Settings modal
      • Queue
      • Topbar Stats
      • Menu
        • Power-Ups!
        • Quick Replies
  • INTEGRATIONS
    • Ebbot Live Chat in Zendesk
      • Setup guide
    • Active Directory - SAML
    • Configure SAML in Azure
Powered by GitBook
On this page
  • Enabling the Sitevision Rest API
  • Settings in Ebbot
  • Why would you want to change the Root node id?
  • What gets scraped?

Was this helpful?

  1. EbbotGPT
  2. Knowledge
  3. Source types

Sitevision API

PreviousTOPdesk APINextSharePoint API

Last updated 6 months ago

Was this helpful?

Enabling the Sitevision Rest API

Ebbot utilizes the Sitevision REST API to fetch Sitevision content and convert it to Ebbot documents for EbbotGPT to generate responses from. In order to fetch information, the REST API must be enabled within Sitevision. This can be done in Sitevision's edit mode:

  1. Click the cog wheel icon in the top bar and select site settings

  1. Under 'Integration' - select REST-API

  1. Check 'Enable REST-API', adjust any restrictions to the API you would like to apply and click OK.

This enables the API, for more information about additional configuration, please consult the Sitevision help & documentation:

Settings in Ebbot

There are multiple settings in Ebbot for the Sitevision connection, to control which content you would like the scraper to fetch. Here is a closer look at each setting:

Domain - Required

This is the domain of your site. Enter only the domain without protocol.

Example: mysite.domain.com

The scraper uses the HTTPS protocol when doing API calls, adding https:// or http:// before the domain will not work.

Username / Password - Optional

If your Rest-API is not publicly accessible, you would enter the username / password to a user that has access to the API. This is marked as optional since this varies between sites, but if the API is not set to public, these credentials are required.

Root node id - Optional

This is where the scrape will start. By default it uses the root node of your site, which means this can be left blank if you want to include the full site.

If you would like to start the scraping process at a different part of your site, you can enter the node ID of the page from where it should start.

The scraping process traverses down the site tree from the root node

Only include pages visible in menus

Checking this box will exclude any pages that have been hidden from the navigation menu in Sitevision

Pages to exclude

Add the page ID's of any pages you want to exclude. If you want to exclude the specific page but include its subpages, deselect the 'Exclude subpages' checkbox.

Getting the ID of a page

There are two primary ways to get the ID of a page.

  1. From the address bar in the Sitevision editor. When in Sitevision edit mode, the ID is the final part of the URL: https://mysite.example.com/edit/2.11fcab81189aff705752d89f

  2. From the browsers console: By opening the page and running `window.sv.PageContext.pageId` in the developer console, it will output the ID of the current page.

Why would you want to change the Root node id?

In some cases you might not want to start at the root and only grab certain parts of the site.

Let’s say that we only want the EbbotGPT have knowledge about “Miljökämpen”, we would enter that page’s id.

What gets scraped?

The scraper get’s the following nodes:

  • Text

  • Block

  • Inline

When getting either the block or inline nodes, it gets the HTML name and turns it into the corresponding markdown tag. If there is no corresponding tag, the node gets ignored.

For example:

https://help.sitevision.se/en/siteRestApiSettingsHelp.html
https://developer.sitevision.se/docs/rest-api/model-rest-api