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 update a specific Resource entity identified by its Resource ID. It allows users to specify which fields of the Resource to update by mapping input data to the corresponding Autotask fields. This is useful for automating updates to resources such as employees, assets, or other entities managed within Autotask, enabling integration with other systems or workflows that modify resource data.
Properties
| Name | Meaning |
|---|---|
| Resource ID | The unique identifier of the Resource entity to update. This is required to specify which resource record will be modified. |
| Fields | A mapping configuration that defines which fields of the Resource should be updated and their new values. It supports defining fields manually or using automatic mapping features to align input data with Autotask resource fields. |
Output
JSON
id- The unique identifier of the updated Resource entity.fields- An object containing the updated fields and their new values as stored in Autotask.success- Boolean indicating whether the update operation was successful.
Dependencies
- Requires an Autotask API authentication credential to access the Autotask REST API.
Troubleshooting
- Ensure the provided Resource ID exists in Autotask; otherwise, the update will fail with a 'Resource not found' error.
- Verify that the fields mapped in 'Fields' are valid and allowed to be updated for the Resource entity to avoid validation errors from the API.
- Check that the API credentials are correctly configured and have sufficient permissions to perform update operations on the Resource entity.
- If the node throws an error about unsupported resource, confirm that the 'Resource' parameter is set to 'resource' and the operation is 'update'.
- Network or API rate limiting issues may cause failures; retry or check API usage limits if encountering intermittent errors.