Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node operation retrieves multiple Contract Billing Rule records from the Autotask system. It is useful for scenarios where you need to fetch a list of billing rules associated with contracts, such as for reporting, synchronization, or further processing in workflows. For example, you might use it to get all billing rules to analyze billing configurations or to update related contract data in another system.

Properties

Name Meaning
Fields Defines how to map and select fields from the Contract Billing Rule resource, allowing customization of which fields to retrieve and how to map them.
Get All Determines whether to return all matching Contract Billing Rule records or limit the number of records returned.
Max Records Specifies the maximum number of Contract Billing Rule records to return when 'Get All' is false. The value can range from 1 to 500.
Add Picklist Labels If enabled, adds human-readable label fields for picklist fields in the output, making it easier to understand picklist values.
Add Reference Labels If enabled, adds human-readable label fields for reference fields in the output, improving readability of referenced data.
Select Columns Names or IDs. Allows selection of specific fields to include in the response. If none 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, simplifying access.

Output

JSON

  • id - Unique identifier of the Contract Billing Rule record.
  • fieldName - Various fields of the Contract Billing Rule as defined by the selected or mapped fields.
  • fieldName_label - Human-readable labels for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' options are enabled.
    userDefinedFields - User-defined fields nested or flattened depending on the 'Flatten User-Defined Fields' option.

Dependencies

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

Troubleshooting

  • If no records are returned, verify that the resource and operation parameters are correctly set to 'contractBillingRule' and 'getMany'.
  • Ensure the API credentials are valid and have sufficient permissions to read Contract Billing Rules.
  • If the node returns an error about unsupported resource, confirm that the resource name is exactly 'contractBillingRule'.
  • When selecting specific fields, ensure the field names or IDs are valid; otherwise, the API may return errors or incomplete data.
  • If the maximum records limit is set too low, you might not get all desired data; consider enabling 'Get All' to retrieve all records.

Discussion