- Integrations
- /
- GitBook
- /
- Actions
- /
- Search GitBook Content
ActionGitBookUpdated May 2026
How do I search GitBook documentation?
Short answer: Drop the "GitBook → Search GitBook Content" 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 |
|---|---|---|---|
Query query | string | Required | — |
Sample request
{"query": "{{trigger.query}}"}
Returns
{"items": [{"id": "match_abc","url": "https://docs.x.com/page","title": "Result"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Search GitBook Content.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Search GitBook Content.
What does the Search GitBook Content action do in GitBook?
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.
What inputs does Search GitBook Content require?
Required: Query. 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 Search GitBook Content support batch operations?
Yes. Run Search GitBook 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
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.
ActionList GitBook Spaces
Returns every space visible to the connected user with name, organisation, recent activity. Useful for resolving space IDs at workflow setup.
Send search gitbook content from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.