Actions100
- Activity Log Actions
- Article Actions
- Asset Actions
- Asset Layout Actions
- Asset Layout Field Actions
- Asset Password Actions
- Card Actions
- Company Actions
- Expiration Actions
- Folder Actions
- IP Address Actions
- List Actions
- Magic Dash Actions
- Matcher Actions
- Network Actions
- Password Folder Actions
- Procedure Actions
- Procedure Task Actions
- Public Photo Actions
- Rack Storage Actions
- Rack Storage Item Actions
Overview
This node interacts with the Hudu REST API to manage various resources, including articles. Specifically, the "Unarchive" operation for the "Article" resource allows users to restore an archived article back to an active state. This is useful in scenarios where articles were previously archived (e.g., for cleanup or organizational purposes) but need to be reinstated for editing, viewing, or further processing.
Practical examples:
- A knowledge base manager wants to unarchive a previously archived help article to update its content.
- An IT documentation team restores archived procedural documents to make them available again for their staff.
Properties
| Name | Meaning |
|---|---|
| Article ID | The unique identifier of the article to unarchive. This is required to specify which archived article should be restored. |
Output
The node outputs JSON data representing the result of the unarchive operation on the specified article. The output typically includes details about the article after it has been unarchived, such as its current status and metadata.
If multiple input items are processed, each item's output is paired with the corresponding input item index.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating requests to the Hudu REST API.
- The base URL for the Hudu API must be configured in the node credentials.
- No other external dependencies are indicated.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Article ID will likely cause the API to return an error.
- Missing or incorrect API authentication credentials will prevent successful communication with the Hudu API.
- Network connectivity issues can cause request failures.
Error messages:
"The resource \"articles\" is not known!"— This would occur if the resource parameter is incorrectly set; ensure "articles" is selected.- API errors returned from Hudu (e.g., 404 Not Found if the article ID does not exist) will be surfaced as node errors.
Resolutions:
- Verify that the Article ID is correct and corresponds to an archived article.
- Confirm that the API key and base URL credentials are properly configured.
- Use the node's "Continue On Fail" option to handle errors gracefully when processing multiple items.
Links and References
- Hudu API Documentation (general reference for API endpoints and authentication)
- n8n documentation on creating custom nodes for further customization guidance