Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

The node retrieves multiple Contract Role Cost records from the Autotask system. It is useful for scenarios where users need to fetch a list of contract role cost entries, for example, to analyze cost data, generate reports, or synchronize contract role costs with other systems.

Properties

Name Meaning
Fields Defines which fields of the Contract Role Costs resource to map and include in the output. Supports custom mapping and selection of specific fields.
Get All Determines whether to return all available Contract Role Cost records or limit the number of records returned.
Max Records Specifies the maximum number of Contract Role Cost records to return when 'Get All' is false. Value range is 1 to 500.
Add Picklist Labels If enabled, adds human-readable label fields for picklist fields in the output, enhancing readability.
Add Reference Labels If enabled, adds human-readable label fields for reference fields in the output.
Select Columns Names or IDs. Allows selection of specific columns (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 promoted to top-level properties in each record instead of being nested.

Output

JSON

  • id - Unique identifier of the Contract Role Cost record.
    - Each selected field from the Contract Role Cost resource as specified by the 'Fields' and 'Select Columns' properties._label - Human-readable label for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' is enabled.userDefinedFields - User-defined fields nested under 'userDefinedFields' or promoted to top-level if 'Flatten User-Defined Fields' is enabled.

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 'contractRoleCosts' and 'getMany'.
  • Ensure the API credentials are valid and have sufficient permissions to read Contract Role Costs.
  • If the node returns an error about unsupported resource, confirm that the resource name is exactly 'contractRoleCosts'.
  • When selecting specific fields, ensure the field names or IDs are valid and exist in the Autotask Contract Role Costs schema.

Discussion