---
title: GitBook Integration for Docs Import | usedocs
description: Import GitBook documentation into usedocs as drafts for cited chat and help-center workflows. Token + space setup.
image: "https://usedocs.app/og.png"
url: "https://usedocs.app/integrations/gitbook"
---

Integration · Updated 2026-08-12

# GitBook integration for usedocs

GitBook remains an excellent docs home. usedocs GitBook import helps you reuse that content for cited support chat and gap operations.

Need help?

Email [hello@usedocs.app](mailto:hello@usedocs.app) for product questions, setup help, sales, partnerships, or security reports.

TL;DR

## Short answer

Import a GitBook space into usedocs to seed help articles and retrieval without rewriting your entire portal. Provide a token and space id, import as drafts, review, then publish or keep GitBook as the public SoR and crawl it instead.

## Overview

Teams often want AI on GitBook content without abandoning GitBook UX. You can crawl the public site URL, or import via API into usedocs drafts for editing inside usedocs. Import is best when you want CMS operations in usedocs; crawl is best when GitBook stays canonical. Prefer public crawl when GitBook is the reader experience customers already love. Use API import when you need editorial workflows inside usedocs or offline spaces. After major GitBook reorgs, broken paths create retrieval misses — re-run import/crawl and spot-check top FAQs. Cross-link the GitBook alternative page for buyers comparing CMS vs agent jobs.

## What this integration does

### Space import

Pull pages from a GitBook space into draft articles for review. Keep configuration documented in your internal runbook so new teammates can reinstall the integration without reverse-engineering the dashboard.

### Chat readiness

Once published or indexed, content participates in retrieval for the widget. Keep configuration documented in your internal runbook so new teammates can reinstall the integration without reverse-engineering the dashboard.

### Parallel to crawl

You can also add the public GitBook URL as a website source without API import. Keep configuration documented in your internal runbook so new teammates can reinstall the integration without reverse-engineering the dashboard.

## Setup

   01

**Create a GitBook token** With read access to the target space only.

   02

**Run import in usedocs** Help center import → GitBook → token + space id → import as drafts.

   03

**Review drafts** Fix formatting, remove internal notes, approve publish if hosting in usedocs.

   04

**Test chat** Ask questions that only those pages answer; check citations.

## Limits and plan notes

- Imports create drafts — humans approve customer-facing publish.
- API rate limits and space size affect duration.
- Styling/components from GitBook may not map 1:1.
- Keep tokens scoped and rotatable.

## Not for you if…

If you only need chat on a public GitBook site, start with URL crawl — simpler than API import. If you need perfect visual parity with GitBook themes, keep GitBook as the reader experience.

## FAQ

### Crawl vs import?

Crawl indexes the public site; import brings content into usedocs articles for editing/hosting.

### Will GitBook stay updated?

Re-import or re-crawl after major doc releases.

### Can we keep GitBook public?

Yes — many teams do.

### Citations point where?

To indexed sources/articles depending on path.

### Auth walls?

Private GitBook spaces need valid tokens; public crawl needs publicly reachable pages.

### Related alternative page?

See the GitBook alternative comparison for buyer fit.

## Connect in the dashboard

Start free, add your docs, then configure integrations under the bot settings.

				 Open dashboard

```json
[
  {
    "@context": "https://schema.org",
    "@type": "BreadcrumbList",
    "itemListElement": [
      {
        "@type": "ListItem",
        "position": 1,
        "name": "Home",
        "item": "https://usedocs.app/"
      },
      {
        "@type": "ListItem",
        "position": 2,
        "name": "Integrations",
        "item": "https://usedocs.app/integrations/"
      },
      {
        "@type": "ListItem",
        "position": 3,
        "name": "GitBook integration for usedocs",
        "item": "https://usedocs.app/integrations/gitbook"
      }
    ]
  },
  {
    "@context": "https://schema.org",
    "@type": "WebPage",
    "name": "GitBook Integration for Docs Import | usedocs",
    "description": "Import GitBook documentation into usedocs as drafts for cited chat and help-center workflows. Token + space setup.",
    "url": "https://usedocs.app/integrations/gitbook",
    "dateModified": "2026-08-12"
  },
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "Crawl vs import?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Crawl indexes the public site; import brings content into usedocs articles for editing/hosting."
        }
      },
      {
        "@type": "Question",
        "name": "Will GitBook stay updated?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Re-import or re-crawl after major doc releases."
        }
      },
      {
        "@type": "Question",
        "name": "Can we keep GitBook public?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Yes — many teams do."
        }
      },
      {
        "@type": "Question",
        "name": "Citations point where?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "To indexed sources/articles depending on path."
        }
      },
      {
        "@type": "Question",
        "name": "Auth walls?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "Private GitBook spaces need valid tokens; public crawl needs publicly reachable pages."
        }
      },
      {
        "@type": "Question",
        "name": "Related alternative page?",
        "acceptedAnswer": {
          "@type": "Answer",
          "text": "See the GitBook alternative comparison for buyer fit."
        }
      }
    ]
  }
]
```