- Integrations
- /
- GitBook
- /
- Actions
- /
- List GitBook Spaces
ActionGitBookUpdated May 2026
What GitBook spaces can I access?
Short answer: Drop the "GitBook → List GitBook Spaces" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
|---|---|---|---|
Limit limit | string | Optional | — |
Sample request
{"limit": "{{trigger.limit}}"}
Returns
{"items": [{"id": "spc_abc","urls": {"app": "https://app.gitbook.com/o/.../s/spc_abc"},"title": "Docs","visibility": "public"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List GitBook Spaces.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List GitBook Spaces.
What does the List GitBook Spaces action do in GitBook?
Returns every space visible to the connected user with name, organisation, recent activity. Useful for resolving space IDs at workflow setup.
What inputs does List GitBook Spaces require?
List GitBook Spaces has no required inputs. Sensible defaults are applied if you leave fields blank.
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 List GitBook Spaces support batch operations?
Yes. Run List GitBook Spaces 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
Other GitBook actions.
Action
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.
ActionSearch 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.
Send list gitbook spaces from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.