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 to manage various resources, including articles. Specifically, for the "Article" resource and the "Delete" operation, it deletes an article identified by its unique ID. This is useful in scenarios where you want to automate content management workflows, such as removing outdated or irrelevant documentation articles from your knowledge base.
Practical examples:
- Automatically deleting articles that are no longer valid after a product update.
- Cleaning up test or draft articles created during content development.
- Integrating with other systems to remove articles when related data is deleted elsewhere.
Properties
| Name | Meaning |
|---|---|
| Article ID | The unique identifier of the article to delete. This must be provided to specify which article to remove. |
Output
The node outputs a JSON array containing the response from the Hudu API after attempting to delete the specified article(s). Each item in the output corresponds to an input item processed and includes the result of the deletion operation.
If the deletion is successful, the output typically contains confirmation details or status information returned by the API. If there is an error (e.g., article not found), the output will include error messages accordingly.
The node does not output binary data.
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 beyond the Hudu API and proper authentication.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Article ID will cause the API to return an error.
- Missing or incorrect API key or base URL configuration will lead to authentication failures.
- Network connectivity problems can prevent the node from reaching the Hudu API.
Error messages:
"The resource "articles" is not known!"— This indicates the resource parameter was incorrectly set; ensure "articles" is selected.- API errors related to authorization or permissions usually indicate issues with the API key or user rights.
- Errors about missing required parameters mean the Article ID was not provided or is empty.
Resolutions:
- Double-check the Article ID value for correctness.
- Verify API credentials and base URL in the node settings.
- Ensure the API key has sufficient permissions to delete articles.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.
Links and References
- Hudu API Documentation (for detailed API endpoints and responses)
- n8n Documentation on HTTP Request Nodes (for understanding API integration basics)