Actions24
- Author Actions
- Book Actions
- Edition Actions
- List Actions
- Publisher Actions
- Series Actions
- User Actions
Overview
This node integrates with the Hardcover API to retrieve book data based on specific criteria. The "Get Book(s) By Status And User ID" operation allows users to fetch books filtered by their reading status (e.g., Want to Read, Currently Reading) and associated user ID. This is useful for applications managing personal reading lists, tracking user progress, or building personalized book recommendations.
Practical examples include:
- A reading app showing a user's current reading list.
- A dashboard displaying books a user has marked as "Read".
- Syncing user-specific book statuses from an external service into n8n workflows.
Properties
| Name | Meaning |
|---|---|
| Status | The reading status of the book. Options: "Want to Read", "Currently Reading", "Read", "Did Not Finish". Determines which subset of books to retrieve based on user reading progress. |
| User ID | Numeric identifier of the user whose books are being queried. Used to filter books belonging to a specific user. |
Output
The node outputs an array of JSON objects, each representing a book matching the specified status and user ID. Each output item contains detailed information about a book as returned by the Hardcover API, such as title, author, edition, publisher, and other metadata depending on the API response.
If the node encounters errors during execution and is configured to continue on failure, it outputs JSON objects containing an error field with the error message.
No binary data output is indicated in the source code.
Dependencies
- Requires an active connection to the Hardcover API via an API key credential.
- The node depends on internal helper functions (
executeSearchOperationandexecuteResourceOperation) to perform API calls. - Proper configuration of the Hardcover API credentials within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid user ID or status value may result in empty results or API errors.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors thrown by the API or network issues are caught and can be output as JSON with an
errorproperty if "Continue On Fail" is enabled. - To resolve errors, verify API credentials, ensure correct input parameters, and check network access.
- Errors thrown by the API or network issues are caught and can be output as JSON with an
Links and References
- Hardcover API Documentation (Replace with actual URL)
- n8n documentation on Creating Custom Nodes