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 integrates with the Hudu REST API, allowing users to perform various operations on different resources within Hudu. Specifically for the Article resource and the Archive operation, the node enables archiving an article by its unique ID. Archiving typically marks the article as inactive or hidden without deleting it permanently, which is useful for content lifecycle management.
Common scenarios include:
- Automatically archiving outdated or deprecated articles in a knowledge base.
- Managing article visibility based on workflow triggers.
- Organizing documentation by moving old articles out of active lists.
Example: You have a set of articles representing product manuals. When a product version is retired, you can archive related articles to keep the knowledge base current without losing historical data.
Properties
| Name | Meaning |
|---|---|
| Article ID | The unique identifier of the article to be archived. This is required to specify which article to archive. |
Output
The node outputs JSON data representing the result of the archive operation on the specified article. Typically, this includes confirmation details such as the article's ID, status, or metadata indicating it has been archived.
If the node supports binary data output (not indicated here), it would represent any file or media associated with the article, but for the archive operation, the output is purely JSON.
Dependencies
- Requires connection to the Hudu REST API.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL for the Hudu API must be set in the node credentials.
- No other external dependencies are indicated.
Troubleshooting
- Invalid Article ID: If the provided Article ID does not exist or is malformed, the API will likely return an error. Ensure the ID is correct and corresponds to an existing article.
- Authentication Errors: Missing or invalid API key will cause authentication failures. Verify that the API key credential is correctly configured.
- Resource Not Known Error: If the resource parameter is incorrect or misspelled, the node throws an error stating the resource is unknown.
- API Rate Limits or Network Issues: Temporary failures may occur due to network problems or API rate limits; retrying or checking connectivity may help.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.
Links and References
- Hudu API Documentation — Official API docs for understanding available endpoints and request formats.
- n8n Documentation — General guidance on using and configuring nodes in n8n workflows.