Waterflai
  • Welcome to Waterflai
  • Getting Started
    • Concepts
    • Quickstart
  • Providers
    • Providers Overview
    • Providers setup
    • AI models
    • Choose the right models
  • Knowledge
    • Knowledge Overview
    • Knowledge connectors
    • Knowledge collections
  • Studio
    • Studio Overview
    • Studio Builders
      • Light Builder
      • Dream Builder
      • Workflow Builder
      • Flow components (nodes)
        • Input Node
        • Output Node
        • LLM model Node
        • Multimodal LLM Node
        • Dall-E 2 (image generation) Node
        • Dall-E 3 (image generation) Node
        • Sora video generation Node
        • Text-to-Speech (TTS) Node
        • Speech-to-Text (STT) Node
        • OCR Node
        • Agent Node
        • Reranker Node
        • Knowledge retrieval Node
        • Vector store insert Node
        • Vector store record delete Node
        • Gitbook loader
        • Notion Database Node
        • Figma Node
        • Webpage scraper Node
        • Sitemap Scraper Node
        • API Request Node
        • Document metadata extraction Node
        • Document metadata update Node
        • Character splitter Node
        • HTML splitter Node
        • Markdown Splitter
        • Calculator tool Node
        • Text as tool Node
        • Knowledge retrieval tool Node
        • Conditional Node
        • Iteration loop Node
      • Testing and Debugging
    • Publishing
    • Integration with API
    • Embedding in website
  • Analytics
    • Analytics Overview
    • Dashboards
    • Logs
  • Administration
    • Organization users
    • Workspace
    • Security and permissions
  • Troubleshooting
    • Support
Powered by GitBook
On this page
  • Overview
  • Configuration
  • Best Practices
  • Common Issues
  1. Studio
  2. Studio Builders
  3. Flow components (nodes)

Gitbook loader

Overview

The GitBook Loader Node allows you to extract content from GitBook documentation pages. It can either load a single page or recursively load all pages from a GitBook documentation site, making it ideal for creating knowledge bases from GitBook documentation.

Usage cost: 1 credit for unique page / 10 credits for whole documentation

Configuration

Settings

  1. GitBook URL

    • URL to the GitBook documentation

    • Can be a specific page URL or root URL when loading all paths

    • Required field

    • Supports variable interpolation

  2. Load Options

    • Load All Paths: Toggle to recursively load all pages

      • When enabled: URL must be the GitBook root

      • When disabled: Loads only the specified page

Output Ports

  1. documents (List[Document]): List of Document objects containing:

    • Page content

    • Metadata (URL, title, etc.)

  2. documents_content (List[string]):

    • List of extracted text content

    • Content only, without metadata

Best Practices

  1. URL Configuration

    • Use root URL when loading all paths

    • Ensure URLs are accessible (public documentation)

    • Verify URL format before execution

  2. Content Loading

    • Use single page loading for specific content

    • Consider load time for large documentation sites

Common Issues

  • Rate limiting from GitBook servers

  • Memory limitations with large documentation sites

  • Slow loading times for recursive fetching

  • Malformed URLs causing loading failures

PreviousVector store record delete NodeNextNotion Database Node

Last updated 3 months ago