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 detailed information about a specific Contract Rate from the Autotask system using its unique Rate ID. It is useful for scenarios where you need to fetch contract rate details for billing, reporting, or integration purposes. For example, you might use it to get the current rate applied to a contract service or to verify rate details before processing invoices.
Properties
| Name | Meaning |
|---|---|
| Rate ID | The unique identifier of the contract rate to retrieve. This is required to specify which contract rate record to fetch. |
| Add Picklist Labels | Determines whether to include human-readable labels for picklist fields in the output, enhancing readability by adding "_label" fields for such properties. |
| Add Reference Labels | Determines whether to include human-readable labels for reference fields in the output, adding "_label" fields for referenced entities. |
| 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 regardless of selection. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are promoted to top-level properties in the output object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- The unique identifier of the contract rate.name- The name or description of the contract rate.rate- The monetary value or rate amount defined in the contract rate.userDefinedFields- An array of user-defined fields associated with the contract rate, unless flattened.*_label- Human-readable labels for picklist or reference fields, added if enabled in input properties.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- Ensure the provided Rate ID is valid and exists in the Autotask system; invalid IDs will cause errors.
- If no data is returned, verify that the API credentials have sufficient permissions to access contract rate data.
- When selecting specific columns, ensure the field names or IDs are correct; otherwise, the response may omit expected data.
- If picklist or reference labels are not appearing, check that the corresponding boolean properties are enabled.
- Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields; disable flattening if this occurs.