OtherReal-timeUpdated May 2026

GitBook

GitBook documentation site search and reads

GitBook is the docs-as-code platform — markdown-backed documentation sites with branching, AI-assisted authoring, and clean public site rendering. Used by companies for public docs (developer documentation, customer-facing knowledge bases) and internal wikis. Tiny Command exposes three actions, no triggers (GitBook webhooks for page-changed, comment-added events are configured per-space in admin; point at a Tiny Command webhook trigger URL): List Spaces (every space — GitBook's top-level docs container — visible to the connected user), Get Space Content (the page tree of a specific space with each page's title and ID), Search Content (full-text across all spaces the user can see). The connection uses a GitBook API key from User Settings → Integrations. Most cross-app GitBook workflows are read-side: an LLM agent grounds answers in your docs by Search Content + Get Space Content. For docs-as-code authoring, GitBook integrates directly with Git repositories — most write workflows go through git rather than via API.

Connect GitBook

0triggers

3actions

≈ 2 minto set up

Freetier · no card

Actions

Do anything GitBook can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

Action	What it does	Inputs
Get GitBook Space Content	Returns the page tree of a specific GitBook space with each page's title, ID, and slug. Useful for "index our docs site" or "find related pages" agentic workflows.	1 fields	View →
List GitBook Spaces	Returns every space visible to the connected user with name, organisation, recent activity. Useful for resolving space IDs at workflow setup.	1 fields	View →
Search GitBook Content	Full-text search across all spaces the user can see. For RAG-style "agent grounds answer in our docs" workflows or for "find relevant doc page" recommendations in support workflows.	1 fields	View →

Recipes

Pre-built GitBook workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

GitBook → Slack alerts

AI-triage every GitBook event, ping the right channel only when it matters.

GitBook → Google Sheets log

Every event matching a filter, appended to a running spreadsheet.

GitBook → Notion database

Turn GitBook into a Notion-backed source of truth, auto-tagged.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect GitBook once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every GitBook field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the GitBook integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect GitBook to Tiny Command?

Open the Tiny Command workflow builder, drop in a GitBook node, and click Connect. Authorize GitBook once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.

What GitBook triggers does Tiny Command support?

Tiny Command focuses on outbound actions for GitBook today. Use Tiny Command's universal Webhook or Schedule trigger to start GitBook workflows, then run any GitBook action you need.

What GitBook actions can I run from a workflow?

3 GitBook actions are available out of the box, covering other operations like "Get GitBook Space Content". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.

Is the GitBook integration real-time?

GitBook actions execute synchronously inside your workflow. Tiny Command waits for GitBook's API to confirm before continuing to the next step, so downstream nodes can rely on the result.

Do I need to write code to use GitBook with Tiny Command?

No. Every GitBook trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any GitBook API endpoint directly.

How much does the GitBook integration cost?

There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The GitBook integration itself has no per-app surcharge.