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 Procedures. Specifically, for the Procedure resource's Create operation, it allows users to create a new procedure within a specified company context. This is useful in scenarios where organizations want to automate the creation and management of procedural documentation or workflows directly from n8n.
Practical examples include:
- Automatically creating a new procedure when onboarding a new employee.
- Generating procedures based on templates or external triggers.
- Associating procedures with specific companies for multi-tenant environments.
Properties
| Name | Meaning |
|---|---|
| Name | The name/title of the procedure to be created. |
| Additional Fields | Optional extra fields to provide more details about the procedure: |
| - Description: A textual description of what the procedure entails. | |
| - Company Name or ID: Select or specify the company to associate this procedure with. | |
| - Company Template: Boolean flag indicating whether to set both template and remove completion ability to true. | |
| Company Name or ID | The company to which this procedure belongs. Must be selected or specified by ID. |
Output
The node outputs JSON data representing the newly created procedure object as returned by the Hudu API. This typically includes the procedure's unique identifier, name, description, associated company information, and any other metadata provided or generated by the API.
No binary data output is involved.
Dependencies
- Requires an active 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.
- The node uses dynamic option loading to fetch companies for selection.
Troubleshooting
- Common Issues:
- Missing or invalid API key can cause authentication failures.
- Specifying a non-existent company ID will result in errors from the API.
- Required fields like "Name" or "Company Name or ID" not provided will cause validation errors.
- Error Messages:
"The resource \"procedures\" is not known!"indicates an incorrect resource parameter.- API errors related to permissions or invalid data will be passed through; ensure the API key has proper rights.
- Resolutions:
- Verify API credentials and permissions.
- Ensure all required fields are filled correctly.
- Use expressions carefully when specifying IDs to avoid malformed requests.
Links and References
- Hudu API Documentation (for detailed API endpoints and data structures)
- n8n Expressions Documentation (for using expressions in property values)