Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

The node's 'Contract Charge' resource with the 'Get Many' operation retrieves multiple contract charge records from the Autotask system. It is useful for scenarios where users need to fetch a list of contract charges, for example, to analyze billing data, generate reports, or synchronize contract charge information with other systems.

Properties

Name Meaning
Fields Defines which fields of the contract charge records to retrieve and map in the output. Supports custom mapping and selection of specific fields.
Get All Determines whether to return all matching contract charge records or limit the number of records returned.
Max Records Specifies the maximum number of contract charge 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 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 selection of specific fields (by name or ID) to include in the response. If none are selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields If enabled, user-defined fields (UDFs) are promoted to top-level properties in each record instead of being nested inside a userDefinedFields array.

Output

JSON

  • id - Unique identifier of the contract charge record.
    - Requested contract charge fields 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 - User-defined fields nested inside userDefinedFields array, unless 'Flatten User-Defined Fields' is enabled, in which case they appear as top-level properties.

Dependencies

  • Requires an API key credential for Autotask REST API authentication.

Troubleshooting

  • If no records are returned, verify that the contract charges exist and that the API user has permission to access them.
  • If the node returns an error about invalid fields, ensure that the selected fields in 'Fields' and 'Select Columns' are valid for the contract charge resource.
  • If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to retrieve all records in multiple calls.
  • Network or authentication errors may occur if the API key credential is invalid or expired; reconfigure the credential as needed.

Discussion