Ivanti icon

Ivanti

Interact with Ivanti API
Join our community

Actions42

Overview

The Ivanti node for n8n allows you to interact with the Ivanti API, specifically targeting various business objects. When using the Custom Business Object resource with the Get Count operation, this node retrieves the count of records in a specified custom business object, optionally filtered by query parameters. This is useful for reporting, monitoring, or conditional workflows where you need to know how many items match certain criteria.

Example scenarios:

  • Counting open tickets or requests in a custom table.
  • Monitoring the number of records that meet specific conditions (e.g., status, date range).
  • Triggering alerts or actions if the count exceeds a threshold.

Properties

Name Meaning
Business Object Name The name or ID of the custom business object you want to query. Required.
Query Parameters Additional OData query parameters to filter results. Includes:
- Result Filter An expression to filter the results (OData syntax). Example: Status eq 'Open'. Used as $filter in the API request.

Output

The output will be a JSON object containing the count of records matching your criteria. The structure typically looks like:

{
  "count": <number>
}
  • count: The total number of records found for the specified business object and filter.

Dependencies

  • External Service: Requires access to an Ivanti instance with API enabled.
  • API Key/Credentials: Needs valid Ivanti API credentials configured in n8n under the credential type IvantiApi.
  • n8n Configuration: The base URL for the Ivanti API must be set in the credentials.

Troubleshooting

Common issues:

  • Invalid Business Object Name: If the provided business object name does not exist, the API may return a 404 or similar error.
  • Authentication Errors: Incorrect or missing credentials will result in authentication failures.
  • Filter Syntax Errors: Invalid OData filter expressions can cause the API to reject the request.

Error messages and resolutions:

  • "Resource not found" – Check the spelling and existence of the business object name.
  • "Unauthorized" – Verify your API credentials and permissions.
  • "Invalid filter expression" – Review your OData filter syntax for correctness.

Links and References

Discussion