ActionBookStackUpdated May 2026

What books are in this BookStack instance?

Short answer: Drop the "BookStack → List Books" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 BookStack 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
Count count	string	Optional	—

Sample request

{
  "count": "{{trigger.count}}"
}

Returns

{
  "data": [
    {
      "id": 1,
      "name": "Engineering Docs",
      "slug": "engineering"
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Books.

Any of these apps can fire this action as part of a workflow.

Google Sheets → BookStack

2 Google Sheets triggers

HubSpot → BookStack

18 HubSpot triggers

FAQ

Questions about List Books.

What does the List Books action do in BookStack?

Returns every book in the connected BookStack instance with name, description, page count, last update. Useful for resolving book IDs at workflow-build time when creating new pages.

What inputs does List Books require?

List Books 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 BookStack 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 Books support batch operations?

Yes. Run List Books inside a Loop node to process arrays. Tiny Command handles BookStack's rate limits automatically so you don't have to throttle manually.

More actions