Short answer: Drop the "BookStack → Create Page" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Book ID book_id | string | Optional | Either book_id OR chapter_id is required |
Chapter ID chapter_id | string | Optional | — |
Title name | string | Required | — |
Markdown Body markdown | string | Required | — |
{"book_id": "{{trigger.book_id}}","chapter_id": "{{trigger.chapter_id}}","name": "{{trigger.name}}","markdown": "{{trigger.markdown}}"}
{"id": 42,"url": "https://wiki/books/.../page/api-spec","name": "API Spec","slug": "api-spec","book_id": 1}
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.
Triggered by anything in the catalog. Free tier available. No credit card.