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 updates an existing Contract Retainer record in the Autotask system. It is useful for users who need to modify details of a contract retainer, such as changing terms, amounts, or other related fields. For example, a project manager might update the retainer amount or adjust the contract dates to reflect new agreements.
Properties
| Name | Meaning |
|---|---|
| Retainer ID | The unique identifier of the contract retainer to update. This is required to specify which retainer record will be modified. |
| Fields | A resource mapper input that defines which fields of the contract retainer should be updated and their new values. This allows flexible mapping of multiple fields to update in the retainer record. |
Output
JSON
id- The unique identifier of the updated contract retainer.fields- An object containing the updated fields and their new values for the contract retainer.status- The status of the update operation, indicating success or failure.message- Additional information or error messages related to the update operation.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
- Relies on the Autotask API endpoint for contract retainers.
Troubleshooting
- If the Retainer ID is missing or invalid, the node will fail to locate the retainer to update. Ensure the ID is correct and exists in Autotask.
- Incorrect field mappings or unsupported fields in the 'Fields' property may cause API errors. Verify field names and data types match Autotask's contract retainer schema.
- API authentication errors may occur if the API key credential is invalid or expired. Check and update credentials as needed.
- Network or API downtime can cause request failures. Retry after some time or check Autotask service status.