Short answer: You can search gitbook content in GitBook by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitBook Search GitBook 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.
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 | – |
{"query": "{{trigger.query}}"}
{"items": [{"id": "match_abc","url": "https://docs.x.com/page","title": "Result"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.