Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node interacts with the Autotask REST API to perform various operations on different resources. Specifically, for the Resource 'resource' and Operation 'getMany', it retrieves multiple records of the specified resource from Autotask. This is useful for scenarios where you need to fetch lists of resources, such as users, assets, or other entities managed in Autotask, for reporting, synchronization, or automation purposes. For example, you might use this node to get all active resources assigned to a project or to pull a subset of resources based on certain criteria.

Properties

Name Meaning
Fields Defines which fields of the resource to retrieve and map in the output. Supports defining fields manually or using auto-mapping features.
Get All Determines whether to return all matching records or limit the number of records returned.
Max Records Specifies the maximum number of records to return when 'Get All' is false. Range is 1 to 500.
Add Picklist Labels If enabled, adds additional fields with human-readable labels for picklist fields in the output, improving readability.
Add Reference Labels If enabled, adds additional fields with human-readable labels for reference fields in the output.
Select Columns Names or IDs. Allows selecting specific fields to include in the response. If none selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields If enabled, user-defined fields (UDFs) are brought to the top level of each object instead of being nested, simplifying access.

Output

JSON

``

  • id - Unique identifier of each resource record.
    - Each selected field's value for the resource record.
  • userDefinedFields - Array of user-defined fields if not flattened; otherwise, UDFs appear as top-level properties.
  • _label - Additional label fields for picklist or reference fields if enabled.

Dependencies

  • Requires an active Autotask API credential for authentication.

Troubleshooting

  • If the node returns an error about unsupported resource, verify that the resource name is correct and supported by the node.
  • If no records are returned, check the field mappings and filters to ensure they match existing data.
  • API rate limits may cause failures; consider enabling pagination or limiting the number of records.
  • Ensure the API credentials have sufficient permissions to read the requested resource data.

Discussion