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 perform various operations on different resources. Specifically, for the Article resource with the Get operation, it retrieves detailed information about a single article identified by its unique ID. This is useful in scenarios where you need to fetch and use article data within an automation workflow, such as displaying article content, updating records based on article details, or integrating article information into other systems.
Practical examples include:
- Fetching an article's content to send it via email.
- Retrieving article metadata to update a knowledge base.
- Using article details to trigger conditional logic in workflows.
Properties
| Name | Meaning |
|---|---|
| Article ID | The unique identifier of the article to retrieve. This must be provided to get the article. |
Output
The node outputs JSON data representing the article's details as returned by the Hudu API. The structure typically includes fields such as the article's title, content, metadata, creation date, last updated date, author information, and any custom fields associated with the article.
If the node supports binary data output (not indicated here), it would represent attachments or media related to the article, but this is not evident from the provided code.
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:
- Providing an invalid or non-existent Article ID will likely result in an error or empty response.
- Missing or incorrect API key or base URL configuration will cause authentication failures.
- Network connectivity issues can prevent successful API calls.
Error messages:
"The resource "articles" is not known!"— indicates the resource parameter was 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 propagated; verify the Article ID correctness.
- Authentication errors due to missing or invalid API keys require checking the credential setup.
To resolve these, verify input parameters, ensure correct credential configuration, and confirm network access to the Hudu API endpoint.
Links and References
- Hudu API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating and using API credentials