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 updates an existing Role entity in the Autotask system by specifying the Role ID and the fields to update. It is useful for automating role management tasks such as changing role permissions, names, or other attributes programmatically. For example, it can be used to update a role's description or access rights in bulk or as part of a workflow that manages user roles dynamically.
Properties
| Name | Meaning |
|---|---|
| Role ID | The unique identifier of the role to update. This is required to specify which role record will be modified. |
| Update Fields | A resource mapper input that defines which fields of the role should be updated and their new values. This allows flexible and dynamic updates of role properties. |
Output
JSON
id- The unique identifier of the updated role.name- The name of the role after update.description- The description of the role after update.permissions- The permissions or access rights assigned to the role after update.updatedAt- Timestamp indicating when the role was last updated.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the Role ID is invalid or does not exist, the node will throw an error indicating the role could not be found. Verify the Role ID is correct.
- If required update fields are missing or invalid, the API may reject the request. Ensure all mandatory fields for update are provided and valid.
- Authentication errors may occur if the API key credential is missing or expired. Check the credential configuration and renew if necessary.
- Network or API downtime can cause request failures. Retry after some time or check the Autotask service status.
Links
- Autotask Roles API Documentation - Official documentation for the Roles resource in the Autotask REST API, detailing available fields and operations.