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 retrieves detailed information about a specific Contract Service Unit from the Autotask system using its unique Service Unit ID. It is useful for workflows that need to fetch and process contract-related service unit data, such as billing, service management, or contract auditing. For example, a user can automate the retrieval of service unit details to update internal records or trigger further actions based on contract service unit attributes.
Properties
| Name | Meaning |
|---|---|
| Service Unit ID | The unique identifier of the contract service unit to retrieve. This is a required input to specify which service unit's details to fetch. |
| Add Picklist Labels | Determines whether to automatically add human-readable '_label' fields for picklist fields in the response. This helps interpret picklist values more easily. No labels are added for empty values. |
| Add Reference Labels | Determines whether to automatically add human-readable '_label' fields for reference fields in the response. This makes reference fields easier to understand. No labels are added for empty values. |
| 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 | Determines whether user-defined fields (UDFs) should be brought up to the top level of the returned object instead of being nested inside a userDefinedFields array. This simplifies access to UDFs. |
Output
JSON
id- The unique identifier of the contract service unit.name- The name of the contract service unit.description- Description or details about the service unit.picklist_field_label- Human-readable label for picklist fields if 'Add Picklist Labels' is enabled.reference_field_label- Human-readable label for reference fields if 'Add Reference Labels' is enabled.userDefinedFields- User-defined fields nested inside userDefinedFields array or flattened to top-level if 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Service Unit ID is invalid or not found, the node will throw an error indicating the resource could not be retrieved. Verify the ID is correct.
- If API authentication fails, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
- Selecting specific columns that do not exist may result in incomplete data or errors. Use the 'Select Columns' dropdown to choose valid fields.
- Enabling 'Flatten User-Defined Fields' may cause naming conflicts if UDF names overlap with standard fields; use with caution.
Links
- Autotask REST API Documentation - Official documentation for Autotask API endpoints and data models.