Actions42
- Incident Actions
- Change Actions
- Custom Business Object Actions
- Employee Actions
- Event Actions
- Task Actions
Overview
The Ivanti node for n8n allows you to interact with the Ivanti API, specifically targeting various business objects such as Tasks. The Task: Get Count operation retrieves the number of Task records that match specified criteria from your Ivanti environment. This is useful for reporting, monitoring workloads, or triggering automations based on the number of tasks meeting certain conditions.
Example scenarios:
- Counting all open tasks to monitor workload.
- Triggering alerts if the number of overdue tasks exceeds a threshold.
- Integrating with dashboards to display task statistics.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | A collection of additional query options to refine your request. |
| Result Filter | An OData filter expression to limit which tasks are counted (e.g., Status eq 'Open'). |
Output
The output will be a JSON object containing the count of Task records matching the provided filter. The typical structure is:
{
"count": <number>
}
count: The total number of Task records that satisfy the filter criteria.
Dependencies
- External Service: Requires access to an Ivanti instance with the OData API enabled.
- API Credentials: Needs valid Ivanti API credentials configured in n8n under the name
IvantiApi. - Environment Variable: The base URL for the Ivanti instance must be set in the credentials (
baseUrl).
Troubleshooting
- Invalid Credentials: If the API credentials are incorrect or missing, authentication errors will occur. Ensure the
IvantiApicredential is properly configured. - Filter Syntax Errors: Incorrect OData filter expressions in "Result Filter" may result in API errors. Refer to OData filter documentation for correct syntax.
- Network Issues: Connectivity problems between n8n and the Ivanti server can cause timeouts or connection errors.
- Insufficient Permissions: The user associated with the API key must have permission to read Task data.