Actions109
- Activity Logs Actions
- Articles Actions
- 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
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Websites Actions
Procedure Tasks → Get Procedure Tasks
AI-generatedOverview
The "Get Procedure Tasks" operation for the "Procedure Tasks" resource retrieves a list of tasks associated with procedures from the AvantGuard Hudu system. This node is useful in scenarios where you need to automate the extraction of procedure task data, such as reporting, monitoring task completion, or integrating procedure tasks into other workflows. For example, you might use this node to fetch all tasks related to a specific procedure or company and then process or analyze them further within your n8n workflow.
Properties
| Name | Type | Meaning |
|---|---|---|
| Additional Query Parameters | Collection | Optional set of filters to refine the search for procedure tasks. |
| └ Procedure Id | Number | Filter results by a specific procedure's ID. |
| └ Name | String | Filter results by the name of the task. |
| └ Company Id | Number | Filter results by a specific company's ID. |
Output
The output consists of a JSON array where each item represents a procedure task. Each object typically contains fields relevant to a procedure task, such as its ID, name, associated procedure, and company information. The exact structure depends on the API response but generally includes identifiers and descriptive properties for each task.
Example Output Structure:
[
{
"id": 123,
"name": "Review Documentation",
"procedure_id": 456,
"company_id": 789,
// ...other task-specific fields
}
]
Note: The node does not output binary data.
Dependencies
- External Service: Requires access to the AvantGuard Hudu API.
- API Key/Credentials: Needs valid
avantguardHuduApicredentials configured in n8n, including the base URL (baseUrl) for the Hudu instance. - n8n Configuration: Ensure that the credentials are set up in n8n under the appropriate credential type.
Troubleshooting
- Invalid Credentials: If the provided API key or base URL is incorrect, the node will fail to connect. Double-check your credentials in n8n.
- Missing Required Filters: If no tasks are returned, ensure that the filter parameters (such as Procedure Id or Company Id) are correct and correspond to existing records.
- API Errors: Common error messages may include authentication errors (401 Unauthorized), not found errors (404), or server errors (500). Check the API documentation and your query parameters if these occur.
- Network Issues: If the node cannot reach the Hudu API, verify network connectivity and firewall settings.