Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
This node operation retrieves multiple Contract Role Costs records from the Autotask system using an advanced filtering mechanism. It is useful for users who need to query contract role cost data with complex criteria, such as filtering by specific fields or conditions, and control the number of records returned. For example, a user can fetch all contract role costs related to a particular contract or role, or apply custom filters to analyze cost data for reporting or integration purposes.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching records or limit the number of results. |
| Max Records | Specifies the maximum number of records to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A JSON string containing a 'filter' array that defines the query criteria according to the Autotask API's advanced query syntax. This allows complex filtering of contract role costs based on various fields. |
| Add Picklist Labels | If enabled, adds additional fields with human-readable labels for picklist fields in the response, improving readability. |
| Add Reference Labels | If enabled, adds additional fields with human-readable labels for reference fields in the response. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are promoted to top-level properties in each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the contract role cost record.contractID- Identifier of the associated contract.roleID- Identifier of the role associated with the cost.cost- Cost value for the contract role.effectiveDate- Date when the cost becomes effective.expirationDate- Date when the cost expires.userDefinedFields- Array of user-defined fields related to the contract role cost, if not flattened.
_label - Human-readable label for picklist or reference fields, added if enabled in input properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Ensure the 'Advanced Filter' JSON string is correctly formatted and follows the Autotask API query syntax; invalid JSON or incorrect filter structure will cause errors.
- If no records are returned, verify that the filter criteria match existing contract role costs in Autotask.
- When selecting specific columns, ensure the field names or IDs are valid for the Contract Role Costs resource; invalid fields may cause the request to fail.
- If the node returns authentication errors, check that the Autotask API credentials are correctly configured and have sufficient permissions.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing the advanced filter query syntax used in the 'Advanced Filter' property.