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 Resource Role records from the Autotask REST API using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter the resource roles returned. Users can choose to return all matching records or limit the number of results. Additionally, it supports options to include human-readable labels for picklist and reference fields, select specific columns to return, and flatten user-defined fields for easier access. This operation is useful for scenarios where detailed and customized queries on resource roles are needed, such as generating reports, syncing data with other systems, or performing bulk data analysis.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching resource role records or limit the results to a specified maximum number. |
| 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. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the Autotask API query criteria to filter resource roles. This allows complex and precise filtering based on field values. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the response. Empty values do not get labels. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the response. Empty values do not get labels. |
| Select Columns Names or IDs. | Allows selection of specific fields (columns) 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 | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a 'userDefinedFields' array, simplifying access. |
Output
JSON
id- Unique identifier of the resource role record.fieldName- Various fields of the resource role as returned by the Autotask API, depending on selected columns.fieldName_label- Human-readable labels for picklist or reference fields, added if respective options are enabled.userDefinedFields- Array of user-defined fields associated with the resource role, unless flattened to top-level properties.
Dependencies
- Requires an Autotask API credential with appropriate permissions to access resource role data.
- Relies on the Autotask REST API endpoint for resource roles.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is well-formed and follows Autotask API filter syntax.
- Requesting too many records without pagination or limits may lead to timeouts or API rate limiting.
- Selecting non-existent columns in 'Select Columns' may result in empty or partial data.
- If labels are not appearing, verify that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled and that the fields have valid values.
- API authentication errors may occur if the Autotask API credentials are missing, expired, or lack necessary permissions.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct advanced filter queries for API calls.