Actions109
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
The "Kickoff Procedure By Id" operation in the "Procedures" resource is designed to initiate (kick off) a specific procedure by its unique identifier. This node is useful in automation scenarios where you need to programmatically start a predefined process or workflow within an external system, such as a maintenance routine, onboarding checklist, or any repeatable business process.
Practical examples:
- Automatically starting a server maintenance procedure when a monitoring alert is triggered.
- Initiating an employee onboarding process when a new hire is added to your HR system.
- Kicking off a compliance checklist for a specific asset after a scheduled interval.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | The ID of the requested procedure. This uniquely identifies which procedure to start. |
| Additional Query Parameters | Collection | Optional parameters to further customize the kickoff request. |
| └ Asset Id | Number | The ID of the asset to attach the process to (optional). |
| └ Name | String | The new name for the procedure (optional). |
Output
The node outputs a json field containing the response from the API after attempting to kick off the specified procedure. The exact structure depends on the external service's API, but typically includes information about the initiated procedure, such as its status, identifiers, and any relevant metadata.
If the node can output binary data, it would represent the raw response or related files, but this operation is expected to return structured JSON.
Dependencies
- External Service: Requires access to the AvantGuard Hudu API.
- API Key/Credentials: Needs valid credentials (
avantguardHuduApi) configured in n8n, including the base URL and authentication details. - n8n Configuration: Ensure that the credentials are set up in n8n under the appropriate credential type.
Troubleshooting
Common Issues:
- Invalid Procedure ID: If the provided Id does not correspond to an existing procedure, the API may return a "Not Found" or similar error.
- Missing Credentials: If credentials are not properly configured, the node will fail with an authentication error.
- Insufficient Permissions: The API key used must have permission to kick off procedures; otherwise, you may receive a "Forbidden" or "Unauthorized" error.
- Incorrect Base URL: If the base URL in credentials is incorrect, requests will fail to reach the intended API endpoint.
Error Messages & Resolutions:
"401 Unauthorized": Check your API credentials and ensure they are correct and active."404 Not Found": Verify that the procedure Id exists and is accessible."400 Bad Request": Ensure all required fields are filled and query parameters are correctly formatted.