ActionGitBookUpdated May 2026

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

Short answer: Drop the "GitBook → Get GitBook Space Content" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 GitBook actions

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get GitBook Space Content support batch operations?

Yes. Run Get GitBook Space Content inside a Loop node to process arrays. Tiny Command handles GitBook's rate limits automatically so you don't have to throttle manually.

More actions