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 Exclusion Role records from the Autotask system. It is useful for scenarios where you need to fetch a list of contract exclusion roles, for example, to analyze or process roles that are excluded from certain contracts. Practical applications include generating reports, syncing data with other systems, or filtering contracts based on exclusion roles.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Contract Exclusion Role resource to map and include in the output. It supports defining fields manually or using auto-mapping features. |
| Get All | Determines whether to return all available Contract Exclusion Role records or limit the number of records returned. |
| Max Records | Specifies the maximum number of Contract Exclusion Role records to return when 'Get All' is set to false. The value must be between 1 and 500. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the output. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the output. |
| 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. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought to the top level of each object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Contract Exclusion Role record.name- Name of the Contract Exclusion Role.description- Description of the Contract Exclusion Role.userDefinedFields- Array of user-defined fields associated with the Contract Exclusion Role, unless flattened.
_label - Human-readable labels for picklist or reference fields, added if enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the resource and operation parameters are correctly set to 'contractExclusionRoles' and 'getMany'.
- Ensure the API credentials are valid and have sufficient permissions to read Contract Exclusion Role data.
- If the node returns an error about unsupported resource, confirm that the resource name is correctly spelled and supported by the node.
- When selecting specific fields, ensure the field names or IDs are valid; otherwise, the API may reject the request or return incomplete data.
- If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to fetch all records.