Autotask icon

Autotask

Interact with Kaseya's Autotask PSA REST API to manage companies, tickets, contracts, and more.

Actions524

Contract Retainer → Update

AI-generated

Overview

This node operation updates an existing Contract Retainer in the Autotask PSA system. It is useful for scenarios where you need to modify details of a contract retainer, such as changing terms, amounts, or other related fields. For example, updating a retainer's billing details or status based on new contract agreements.

Use Case Examples

  1. Updating the billing amount of a contract retainer after a contract amendment.
  2. Changing the status or terms of a contract retainer to reflect new client agreements.

Properties

Name Meaning
Retainer ID The unique identifier of the contract retainer to update. This is required to specify which retainer record to modify.
Dry Run A boolean flag to indicate whether to perform a dry run. When enabled, the node returns a preview of the request without executing the update, useful for testing and validation.
Fields The fields and their values to update on the contract retainer. This uses a resource mapper to define which fields to modify and their new values.

Output

JSON

  • id - The ID of the updated contract retainer.
  • fieldsUpdated - Details of the fields that were updated in the contract retainer.
  • status - The status or result of the update operation, indicating success or failure.

Dependencies

  • Autotask PSA REST API

Troubleshooting

  • Ensure the Retainer ID is valid and exists in the Autotask system to avoid 'not found' errors.
  • If Dry Run is enabled, no changes will be made; disable it to perform actual updates.
  • Check API credentials and permissions to ensure the node can perform update operations on contract retainers.
  • Handle errors gracefully by enabling 'Continue On Fail' to process multiple items without stopping on the first error.

Links

  • Autotask PSA REST API Documentation - Official API documentation for Autotask PSA, useful for understanding available endpoints and data structures related to contract retainers.

Discussion