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 interacts with the Autotask REST API to retrieve detailed information about a specific Resource Role by its ID. It is useful in scenarios where you need to fetch configuration or permission details related to resource roles within Autotask, such as for auditing, reporting, or integration workflows. For example, you can use this node to get the attributes of a resource role to determine access levels or to synchronize role data with another system.
Properties
| Name | Meaning |
|---|---|
| Resource Role ID | The unique identifier of the resource role to retrieve. This is a required input to specify which resource role's details should be fetched. |
| Add Picklist Labels | A boolean option to automatically add human-readable '_label' fields for picklist fields in the response. This helps in understanding picklist values without needing to decode them manually. |
| Add Reference Labels | A boolean option to automatically add human-readable '_label' fields for reference fields in the response. This makes reference fields easier to interpret. |
| 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. This helps optimize data retrieval by limiting the response to relevant fields. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are brought up to the top level of the returned object instead of being nested inside a 'userDefinedFields' array. This simplifies access to UDFs in the output. |
Output
JSON
id- The unique identifier of the resource role.name- The name of the resource role.description- A textual description of the resource role.picklistField_label- Human-readable labels for picklist fields, added if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable labels for reference fields, added if 'Add Reference Labels' is enabled.userDefinedFields- An array of user-defined fields associated with the resource role, unless flattened.userDefinedFieldName- When 'Flatten User-Defined Fields' is enabled, UDFs appear as top-level properties with their respective names.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the node returns an error indicating the resource role 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 access resource role information.
- Errors related to picklist or reference labels may occur if the fields do not have associated labels; disabling the label options can help isolate the issue.
- If user-defined fields are not appearing as expected, verify the 'Flatten User-Defined Fields' option and the structure of the data in Autotask.
Links
- Autotask Resource Roles API Documentation - Official Autotask documentation describing the Resource Roles resource and its fields.
- n8n Autotask Node Documentation - General documentation for the Autotask node in n8n, including usage and configuration.