Actions40
- Book Actions
- Page Actions
- Chapter Actions
- Shelf Actions
- User Actions
- Role Actions
- Attachment Actions
- Tag Actions
Overview
This node integrates with the BookStack API to manage content resources such as pages, books, chapters, shelves, users, roles, attachments, and tags. Specifically, for the Page - Delete operation, it allows users to delete a page resource by specifying its unique ID.
Common scenarios where this node is beneficial include:
- Automating content management workflows in BookStack, such as removing outdated or irrelevant pages.
- Integrating BookStack page deletion into larger automation pipelines, e.g., cleaning up documentation pages after a project ends.
- Managing content lifecycle programmatically without manual intervention in the BookStack UI.
Example use case:
- Automatically deleting a page titled "API Documentation Draft" once the final version is published elsewhere.
Properties
| Name | Meaning |
|---|---|
| Tool Description | Choose how to determine the resource and operation: - Set Automatically - Set Manually |
| Request Description | (Shown if Tool Description is "Set Automatically") Describe your request in natural language, e.g., "Delete the page with ID 123". The system will parse this to select the resource and operation automatically. |
| ID | The unique identifier of the page to delete. Required for delete operations. |
Output
The node outputs JSON data representing the response from the BookStack API after attempting to delete the specified page. Typically, a successful delete operation returns an empty object or confirmation message indicating the resource was deleted.
If the node encounters an error during deletion, the output JSON will contain an error field with the error message.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a BookStack instance via its API.
- Needs an API authentication token credential configured in n8n with:
- Base URL of the BookStack API.
- Authorization token and secret.
- The node uses HTTP DELETE requests to the endpoint
/pages/{id}where{id}is the page ID.
Troubleshooting
- Missing or invalid ID: If the ID property is not provided or incorrect, the API will return an error indicating the resource could not be found. Ensure the correct page ID is supplied.
- Authentication errors: If the API token or base URL is misconfigured, the node will fail with authorization errors. Verify credentials are correctly set.
- Resource not found: Attempting to delete a non-existent page ID will result in a 404 error. Confirm the page exists before deletion.
- Permission issues: The API user must have sufficient permissions to delete pages; otherwise, the request will be denied.
- Automatic mode parsing failures: When using automatic tool description mode, ambiguous or incomplete descriptions may cause incorrect operation/resource selection. Use manual mode or provide clear descriptions.