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 "Procedure" resource of the Hudu REST API, specifically supporting the Delete operation. It allows users to delete a procedure by specifying its unique Procedure ID. This is useful in automation workflows where outdated or irrelevant procedures need to be programmatically removed from the Hudu system.
Common scenarios:
- Automatically cleaning up procedures that are no longer needed.
- Integrating with ticketing or incident management systems to remove procedures after resolution.
- Managing lifecycle of documentation by deleting deprecated procedures as part of a scheduled workflow.
Example:
A user can set up an n8n workflow that triggers on certain conditions (e.g., a procedure marked as obsolete) and uses this node to delete that procedure by providing its ID.
Properties
| Name | Meaning |
|---|---|
| Procedure ID | The numeric ID of the procedure to delete |
Output
The node outputs a JSON array containing the response from the API after attempting to delete the specified procedure. Typically, this will include confirmation of deletion or details about the deleted procedure. If the deletion fails, the output may contain error information.
No binary data output is produced by this operation.
Dependencies
- Requires connection to the Hudu REST API.
- Needs an API key credential configured in n8n for authentication.
- The base URL for the Hudu API must be set in the node credentials.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Procedure ID will result in an error from the API.
- Missing or incorrect API key credential configuration will cause authentication failures.
- Network connectivity issues can prevent the node from reaching the Hudu API.
Error messages:
"The resource "procedures" is not known!"— indicates the resource parameter was incorrectly set; ensure "procedures" is selected.- API errors related to authorization or permissions typically indicate problems with the API key or user rights.
- If the node throws an error about missing parameters, verify that the Procedure ID is provided and is a valid number.
To resolve errors:
- Double-check the Procedure ID input.
- Verify API credentials and permissions.
- Ensure network access to the Hudu API endpoint.
Links and References
- Hudu API Documentation (for detailed API endpoints and responses)
- n8n Documentation on Creating Custom Nodes