Short answer: You can list gitbook spaces in GitBook by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitBook List GitBook Spaces 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 |
|---|---|---|---|
Limit limit | string | Optional | – |
{"limit": "{{trigger.limit}}"}
{"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.
Any of these apps can fire this action as part of a workflow.