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 "Get" operation to retrieve details about a specific procedure by its ID. It is useful in scenarios where you need to fetch detailed information about a particular procedure stored in Hudu, such as for documentation, auditing, or integration purposes.
For example, you might use this node to:
- Retrieve a procedure's full details to display or process in another workflow.
- Automate fetching procedures for reporting or compliance checks.
- Integrate procedure data into other systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Procedure ID | The unique numeric identifier of the procedure to retrieve. This is a required field. |
Output
The node outputs JSON data representing the retrieved procedure's details. The structure typically includes all relevant fields describing the procedure as returned by the Hudu API, such as its name, description, steps, metadata, and any custom fields associated with it.
If the node supports binary data output (not indicated here), it would represent attachments or files related to the procedure, but based on the provided code and properties, the output is purely JSON.
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 Procedure ID will cause the API call to fail.
- Incorrect or expired API key will result in authentication errors.
- Network connectivity problems can prevent successful API calls.
- Using an unknown resource or operation will throw an error indicating the resource is not known.
Error messages:
"The resource \"procedures\" is not known!"— indicates the resource parameter was incorrect or unsupported.- API errors from Hudu (e.g., 404 Not Found if the procedure ID does not exist) will be propagated; ensure the Procedure ID is valid.
- Authentication errors due to invalid API keys require checking and updating the credentials.
To resolve errors, verify that the Procedure ID is correct, the API key is valid, and the network connection to Hudu is stable.
Links and References
- Hudu API Documentation (for detailed info on procedures endpoint)
- n8n Documentation on Creating Custom Nodes