Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Contract Role Costs → Get Many
AI-generatedOverview
This node operation retrieves multiple records of Contract Role Costs from the Autotask PSA system. It is useful for scenarios where users need to fetch a list of contract role cost entries, such as for reporting, auditing, or integration with other systems. For example, a user might want to get all contract role costs associated with a specific contract or within a certain date range.
Use Case Examples
- Fetch all contract role costs for a given contract to analyze cost distribution.
- Retrieve a limited number of contract role cost records for display in a dashboard.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all results or only up to a given limit. |
| Max Records | Maximum number of contract role cost records to return when not returning all. Range is 1 to 500. |
| Add Picklist Labels | Whether to automatically add human-readable labels for picklist fields in the output. |
| Add Reference Labels | Whether to automatically add human-readable labels for reference fields in the output. |
| Select Columns Names or IDs. | Choose which fields to include in the response. If no fields are selected, all fields will be returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Whether to bring user-defined fields up to the top level of each object instead of nested in the 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 assigned to the role in the contract.effectiveDate- Date from which the cost is effective.expirationDate- Date until which the cost is valid.userDefinedFields- Array of user-defined fields related to the contract role cost, if not flattened.picklistLabels- Human-readable labels for picklist fields, if enabled.referenceLabels- Human-readable labels for reference fields, if enabled.
Dependencies
- An API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Common issues include authentication failures due to invalid or missing API credentials. Ensure the API key credential is correctly configured.
- Errors may occur if the resource or operation parameters are incorrect or unsupported. Verify that 'Contract Role Costs' resource and 'Get Many' operation are selected.
- If the maximum records limit is set too high, the API may throttle or reject the request. Use the 'Get All' option carefully or set a reasonable limit.
- If user-defined fields are not appearing as expected, check the 'Flatten User-Defined Fields' option to control their structure in the output.
Links
- Autotask PSA REST API Documentation - Official documentation for the Autotask PSA REST API, useful for understanding available endpoints and data structures.