AvantGuard - HuduInstall

Overview

The Create Procedure From Template operation under the Procedures resource allows users to duplicate an existing procedure template, optionally customizing its name, description, and associating it with a specific company. This is useful for organizations that want to standardize processes but need to quickly generate new procedures based on pre-defined templates, either globally or for particular companies.

Practical examples:

• A managed service provider (MSP) wants to create a new onboarding procedure for a client, using their standard onboarding template but with a custom name and description.
• An IT department needs to roll out a new security checklist across multiple subsidiaries, each as a separate procedure linked to the relevant company.

Properties

Name	Type	Meaning
Id	Number	The ID of the template procedure to duplicate.
Additional Query Parameters	Collection	Optional parameters to further customize the new procedure. Includes:
└─ Company Id	Number	The ID of the company for the new procedure. If omitted, creates a global template.
└─ Name	String	The new name for the duplicated procedure.
└─ Description	String	The new description for the duplicated procedure.

Output

The node outputs a json object containing the details of the newly created procedure. While the exact structure depends on the API response, typical fields may include:

{
  "id": 123,
  "name": "New Procedure Name",
  "description": "Custom description",
  "company_id": 456,
  // ...other metadata fields returned by the API
}

• If binary data is ever output, it would represent the exported procedure file or similar, but this node primarily returns JSON.

Dependencies

• External Service: Requires access to the AvantGuard Hudu API.
• API Key/Credentials: Needs valid avantguardHuduApi credentials configured in n8n, including the baseUrl.
• n8n Configuration: Ensure the credentials are set up in n8n under the correct credential type.

Troubleshooting

Common Issues:

• Invalid Template ID: If the provided template ID does not exist, the API will likely return a "not found" error.
• Missing Credentials: If credentials are not configured or invalid, authentication errors will occur.
• Insufficient Permissions: The user associated with the API key must have permission to create procedures.

Error Messages & Resolutions:

• "404 Not Found": Check that the template ID is correct and exists.
• "401 Unauthorized": Verify that the API credentials are correctly set up in n8n.
• "400 Bad Request": Ensure all required fields are filled and query parameters are valid.

Links and References

• Hudu API Documentation (for reference on endpoints and expected responses)
• n8n Credentials Documentation
• AvantGuard - Hudu Node GitHub (if available)