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 update existing procedures within the Hudu system. It allows users to modify various attributes of a procedure such as its name, description, associated company, archival status, and template settings.
Common scenarios for this node include:
- Automating updates to procedure details when organizational changes occur.
- Synchronizing procedure information from other systems or databases.
- Archiving outdated procedures programmatically.
- Adjusting procedure templates and permissions in bulk.
For example, a user might use this node to update the description and company association of a procedure after a rebranding effort or company restructuring.
Properties
| Name | Meaning |
|---|---|
| Procedure ID | The unique numeric identifier of the procedure to update. |
| Update Fields | A collection of fields to update on the procedure: |
| - Archived | Boolean flag indicating whether the procedure should be archived (true) or active (false). |
| - Company Name or ID | Select or specify the company to associate with the procedure. Options are loaded dynamically from companies available in the system. |
| - Company Template | Boolean flag to set both the template status and remove completion ability to true. |
| - Description | New textual description for the procedure. |
| - Name | New name for the procedure. |
Output
The node outputs an array of JSON objects representing the updated procedure(s). Each output item corresponds to one input item processed and includes the updated procedure data as returned by the Hudu API.
If the node encounters errors during execution and is configured to continue on failure, it outputs error messages in JSON format linked to the respective input item.
No binary data output is produced by this node.
Dependencies
- Requires a valid API key credential for authenticating with the Hudu REST API.
- The base URL for the Hudu API must be configured in the node credentials.
- Dynamic options for selecting companies depend on the successful loading of company data via the API.
Troubleshooting
- Invalid Procedure ID: If the specified procedure ID does not exist, the node will throw an error. Verify that the ID is correct and that the procedure exists in Hudu.
- Authentication Errors: Missing or invalid API keys will cause authentication failures. Ensure the API key credential is correctly configured.
- Permission Issues: Insufficient permissions on the API key may prevent updating certain fields. Confirm the API key has adequate rights.
- Invalid Field Values: Providing unsupported values (e.g., non-boolean for boolean fields) can cause errors. Validate input types before execution.
- Network or API Downtime: Temporary connectivity issues or API outages will result in request failures. Retry after some time or check network connectivity.
Links and References
- Hudu API Documentation — Official API reference for understanding procedure endpoints and field definitions.
- n8n Expressions — Guide on using expressions to dynamically set property values in n8n nodes.