Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

The node's 'Get Many' operation for the 'Opportunity' resource retrieves multiple opportunity records from the Autotask system. It allows users to fetch a list of opportunities with control over which fields to include, how many records to return, and whether to include human-readable labels for picklist and reference fields. This operation is useful for scenarios such as reporting, data synchronization, or bulk data processing where multiple opportunity records are needed at once.

Properties

Name Meaning
Fields Defines which fields of the opportunity records to retrieve and map in the output. Supports custom mapping and selection of specific fields.
Get All Determines whether to return all matching opportunity records or limit the number of records returned.
Max Records Specifies the maximum number of opportunity records to return when 'Get All' is false. Range is 1 to 500.
Add Picklist Labels If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the opportunity records.
Add Reference Labels If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the opportunity records.
Select Columns Names or IDs. Allows selection of specific fields to include in the response by choosing from a list or specifying field IDs. If no fields are 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 opportunity object instead of being nested inside a userDefinedFields array.

Output

JSON

  • id - Unique identifier of the opportunity record.
    - Standard or user-defined fields of the opportunity as specified in the Fields property._label - Human-readable label for picklist or reference fields if Add Picklist Labels or Add Reference Labels is enabled.
  • userDefinedFields - Array of user-defined fields if Flatten User-Defined Fields is disabled; otherwise, UDFs appear as top-level properties.

Dependencies

  • Requires an Autotask API key credential for authentication to access the Autotask REST API.

Troubleshooting

  • If no records are returned, verify that the query parameters and field selections are correct and that the Autotask account has opportunity records matching the criteria.
  • If the node throws authentication errors, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
  • Selecting too many fields or requesting a very large number of records may cause performance issues or API rate limiting; consider limiting the number of fields and records.
  • If picklist or reference labels are not appearing, check that the corresponding options (Add Picklist Labels, Add Reference Labels) are enabled and that the fields contain values.

Discussion