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 retrieve version history information for articles. Specifically, the "Get Version History" operation under the "Article" resource fetches the historical versions or changes made to a particular article identified by its unique ID. This is useful in scenarios where you need to audit changes, track updates over time, or restore previous versions of documentation or knowledge base articles.
Practical examples include:
- Auditing who changed an article and when.
- Displaying a timeline of edits for compliance or review purposes.
- Integrating version history data into other workflows or dashboards.
Properties
| Name | Meaning |
|---|---|
| Article ID | The unique identifier of the article whose version history you want to retrieve. This is required. |
| Filters | Optional filters to narrow down the version history entries based on date criteria. Contains: |
| Date Range | Filter history entries by specific dates or ranges. Modes include: - Exact Date: Match entries from a single specific date. - Date Range: Match entries within a start and end date (inclusive). - Preset Range: Choose from common predefined ranges such as last 7 days, last month, today, yesterday, etc. |
Output
The output is a JSON array where each item represents a version history entry for the specified article. Each entry typically includes details such as the version number, timestamp of the change, user who made the change, and possibly a summary or description of what was changed.
If the node supports binary data output (not indicated here), it would represent attachments or related files associated with version history entries, but this operation primarily returns structured JSON data about article versions.
Dependencies
- Requires an active 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 additional external dependencies are indicated.
Troubleshooting
Common Issues:
- Invalid or missing Article ID will cause the operation to fail.
- Incorrect API key or base URL configuration will result in authentication errors.
- Filtering by date range with invalid or improperly formatted dates may return no results or errors.
Error Messages:
"The resource "articles" is not known!"— indicates the resource parameter is incorrect or unsupported.- Authentication errors typically mention invalid API keys or unauthorized access.
- If no version history exists for the given article, the output may be empty rather than an error.
Resolutions:
- Verify that the Article ID is correct and corresponds to an existing article.
- Check API credentials and base URL settings.
- Ensure date filters are correctly formatted and logical (start date before end date).
Links and References
- Hudu API Documentation — for detailed API endpoints and parameters.
- n8n Documentation — for general guidance on using credentials and configuring nodes.