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
The node interacts with the Autotask REST API to retrieve multiple Resource Role records. It supports fetching either all records or a limited number, with options to customize the fields returned, including user-defined fields and picklist/reference labels. This is useful for workflows that need to process or analyze multiple resource roles from Autotask, such as reporting, synchronization with other systems, or bulk data processing.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Resource Role records to retrieve and map in the output. Supports custom mapping and auto-mapping of fields. |
| Get All | Determines whether to return all Resource Role records or limit the number of records returned. |
| Max Records | Specifies the maximum number of Resource Role records to return when 'Get All' is 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 by choosing from a list or specifying IDs via expressions. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are moved to the top level of each record object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Resource Role record.name- Name of the Resource Role.userDefinedFields- Array of user-defined fields associated with the Resource Role, unless flattened.
_label - Human-readable label for picklist or reference fields, added if enabled. - Other fields as specified by the Fields property, including standard and custom fields.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the node returns an error about unsupported resource, ensure the resource parameter is set to 'resourceRole'.
- If no records are returned, verify that the Autotask account has Resource Role data and that the API user has sufficient permissions.
- If the node times out or returns partial data, consider enabling 'Get All' to fetch all records or increasing the 'Max Records' limit up to 500.
- Errors related to field mapping may occur if the selected fields do not exist or are misspelled; verify field names in the Fields property.
- If picklist or reference labels are missing, ensure 'Add Picklist Labels' and 'Add Reference Labels' options are enabled.