Actions31
Overview
This node integrates with the BookStack API to manage various resources such as books, pages, chapters, and shelves. Specifically, the Update Book operation allows users to modify an existing book's details by specifying its ID along with new values for its name and optionally its description.
Common scenarios where this node is useful include:
- Updating metadata of a book in a documentation or knowledge base system.
- Correcting or refining the title or description of a book after creation.
- Automating bulk updates to book information via workflows.
For example, you might use this node to update the name of a book from "Project Docs" to "Project Documentation" and add a description summarizing its contents.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the book to update (required). |
| Name | The new name/title of the book (required). |
| Description | A textual description of the book (optional). |
Output
The node outputs JSON data representing the updated book resource as returned by the BookStack API. This typically includes fields such as the book's ID, name, description, creation and modification timestamps, and other metadata.
No binary data output is produced by this operation.
Dependencies
- Requires access to the BookStack API endpoint.
- Needs an API authentication token credential configured in n8n with appropriate permissions to update books.
- The base URL and authentication tokens must be set in the node credentials to authorize requests.
Troubleshooting
- Missing or invalid ID: If the provided book ID does not exist or is malformed, the API will return an error. Ensure the ID is correct and corresponds to an existing book.
- Authentication errors: If the API token is missing, expired, or lacks update permissions, the request will fail. Verify that the API credentials are correctly configured and have sufficient rights.
- Validation errors: Omitting required fields like the book name or providing invalid data types may cause the API to reject the update. Always provide valid and complete input properties.
- Network issues: Connectivity problems or incorrect base URLs can prevent successful API calls. Confirm network access and correct endpoint configuration.