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 Exclusion Set Excluded Work Type in Autotask by its ID. It is useful for workflows that need to fetch and process exclusion work type data related to contract exclusion sets, such as auditing contract configurations or integrating contract data with other systems.
Properties
| Name | Meaning |
|---|---|
| Excluded Work Type ID | The unique identifier of the contract exclusion set excluded work type to retrieve. |
| Add Picklist Labels | Determines whether to add human-readable label fields for picklist fields in the response, enhancing readability. |
| Add Reference Labels | Determines whether to add human-readable label fields for reference fields in the response. |
| Select Columns Names or IDs. | Specifies which fields to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) are promoted to top-level properties instead of being nested inside a userDefinedFields array. |
Output
JSON
id- The unique identifier of the excluded work type.name- The name of the excluded work type.description- Description or details about the excluded work type.userDefinedFields- Array of user-defined fields related to the excluded work type, unless flattened.
_label - Human-readable labels for picklist or reference fields, added if enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the node returns an error indicating the excluded work type ID is invalid or not found, verify that the provided ID exists in Autotask.
- If no data is returned, check that the API credentials have sufficient permissions to read contract exclusion set excluded work types.
- Errors related to picklist or reference labels may occur if the fields do not have associated labels; disabling label addition can resolve this.
- If user-defined fields are not appearing as expected, verify the 'Flatten User-Defined Fields' option and the structure of the data in Autotask.