Autotask icon

Autotask

Interact with Kaseya's Autotask PSA REST API to manage companies, tickets, contracts, and more.

Actions524

Resource → Get Many (Advanced)

AI-generated

Overview

This node interacts with the Autotask PSA REST API to retrieve multiple records of the 'Resource' entity using advanced filtering options. It supports fetching all records or a limited number based on user input, applying complex JSON-based filters to query the API effectively. This operation is useful for scenarios where users need to extract detailed and specific data about resources managed in Autotask, such as for reporting, data synchronization, or integration with other systems.

Use Case Examples

  1. Retrieve all resources with a specific skill or role by applying an advanced JSON filter.
  2. Fetch a limited number of resource records for quick overview or dashboard display.
  3. Use the advanced filter to get resources that meet multiple criteria, such as availability and department.

Properties

Name Meaning
returnAll Whether to return all results or only up to a given limit.
maxRecords Maximum number of records to return when 'returnAll' is false, ranging from 1 to 500.
advancedFilter A JSON string containing a 'filter' array with Autotask API query criteria to apply complex filtering on the resource records.
addPicklistLabels Whether to automatically add '_label' fields for picklist fields with human-readable values.
addReferenceLabels Whether to automatically add '_label' fields for reference fields with human-readable values.
selectColumns Choose specific fields to include in the response; if none selected, all fields are returned. The ID field is always included.
flattenUdfs Whether to bring user-defined fields up to the top level of each object for easier access.

Output

JSON

  • id - Unique identifier of the resource record.
  • fieldName
    • _label - Human-readable labels for picklist or reference fields if enabled in input properties.

Dependencies

  • Autotask PSA REST API
  • API authentication credentials (API key or integration code)

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to access resource data.
  • Verify the JSON syntax and structure of the 'advancedFilter' property to avoid query errors.
  • If no records are returned, check the filter criteria to ensure they match existing resource data.
  • Be aware of API rate limits; the node attempts to initialize rate tracking but may fall back to local counting if it fails.

Links

Discussion