ActionGitBookUpdated September 2026

How do I fetch a GitBook space's page tree?

Short answer: You can get gitbook space content in GitBook by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitBook Get GitBook Space Content action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get GitBook Space Content in GitBook — start free All 3 GitBook actions

Get GitBook Space Content in GitBook — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Space ID space_id	string	Required	The Space ID assigned by Gitbook. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label.

Sample request

{
  "space_id": "{{trigger.space_id}}"
}

Returns

{
  "pages": [
    {
      "id": "page_abc",
      "path": "intro",
      "title": "Intro"
    }
  ],
  "object": "revision"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get GitBook Space Content.

Any of these apps can fire this action as part of a workflow.

Google Sheets → GitBook

2 Google Sheets triggers

HubSpot → GitBook

18 HubSpot triggers

FAQ

Questions about Get GitBook Space Content.

What does the Get GitBook Space Content action do in GitBook?

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.

What inputs does Get GitBook Space Content require?

Required: Space ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GitBook returns an error?

The run history shows the failed step with its input and the error message GitBook returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Get GitBook Space Content support batch operations?

Run Get GitBook Space Content inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GitBook's rate limits.

More actions

Other GitBook actions.

Action

List GitBook Spaces

Returns every space visible to the connected user with name, organisation, recent activity. Useful for resolving space IDs at workflow setup.

Action

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.

Get GitBook Space Content in GitBook — start free