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 BookStack resources such as books, pages, chapters, shelves, users, roles, attachments, and tags. Specifically for the Book resource with the Delete operation, it allows users to delete a book by specifying its ID.
Common scenarios where this node is beneficial include:
- Automating content management workflows by programmatically deleting outdated or unwanted books.
- Integrating BookStack cleanup tasks into larger automation pipelines.
- Managing BookStack resources without manual intervention via API calls.
Practical example:
- Automatically delete a book from BookStack when a related project is archived in another system.
Properties
| Name | Meaning |
|---|---|
| Tool Description | Choose how to determine the resource and operation: "Set Automatically" or "Set Manually". |
| Request Description | (Shown if "Set Automatically") Describe your request in natural language; the system will infer the resource and operation. Example: "Delete the book with ID 123". |
| ID | The unique identifier of the book to delete. Required for Delete operation. |
Output
The node outputs JSON data representing the response from the BookStack API after attempting to delete the specified book. Typically, this will be an empty object or confirmation of deletion depending on the API's response.
No binary data output is produced by this node.
Example output JSON structure:
{}
or possibly some metadata confirming deletion.
Dependencies
- Requires an API key credential for authenticating with the BookStack API.
- The base URL and authentication tokens must be configured in the node credentials.
- The node uses HTTP DELETE requests to the endpoint
/books/{id}to perform deletions.
Troubleshooting
- Missing or invalid ID: If the ID property is not provided or incorrect, the API call will fail. Ensure the correct book ID is supplied.
- Authentication errors: Verify that the API key/token credentials are correctly set up and have sufficient permissions to delete books.
- Resource not found: If the book ID does not exist, the API may return a 404 error. Confirm the book exists before attempting deletion.
- API endpoint issues: Ensure the base URL is correctly configured and accessible from n8n.
Common error messages:
"error": "Unauthorized"— Check API credentials."error": "Not Found"— Verify the book ID is correct.- Network or timeout errors — Check connectivity and API availability.