Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node interacts with the Autotask REST API to retrieve multiple Contract Ticket Purchase records. It is useful for scenarios where users need to fetch a list of ticket purchases related to contracts, such as generating reports, synchronizing data with other systems, or analyzing purchase trends. For example, a user can retrieve all contract ticket purchases within a certain limit or fetch all available records for further processing.

Properties

Name Meaning
Fields Defines which fields of the Contract Ticket Purchase resource to map and include in the output. Supports defining fields manually or using auto-mapping features.
Get All Determines whether to return all matching Contract Ticket Purchase records or limit the number of records returned.
Max Records Specifies the maximum number of Contract Ticket Purchase records to return when 'Get All' is false. The value must be between 1 and 500.
Add Picklist Labels If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the output.
Add Reference Labels If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the output.
Select Columns Names or IDs. Allows selecting specific fields (columns) to include in the response. If no fields are selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields When enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a userDefinedFields array.

Output

JSON

  • id - Unique identifier of the contract ticket purchase record.
  • fields
    • _label - Human-readable labels for picklist and reference fields if enabled.
  • userDefinedFields - Array of user-defined fields if flattening is disabled.

Dependencies

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

Troubleshooting

  • If no records are returned, verify that the resource and operation parameters are correctly set to 'contractTicketPurchase' and 'getMany'.
  • Ensure the API credentials are valid and have sufficient permissions to read contract ticket purchase data.
  • If the node returns an error about unsupported resource, confirm that the resource name is exactly 'contractTicketPurchase'.
  • When selecting specific fields, ensure the field IDs or names are valid; otherwise, the API may return incomplete data or errors.
  • If the maximum records limit is set too high, the API might throttle or reject the request; try reducing the limit or enabling 'Get All' carefully.

Discussion