Autotask icon

Autotask

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

Actions524

Company → Update

AI-generated

Overview

This node operation updates an existing company record in Kaseya's Autotask PSA system. It is useful for scenarios where you need to modify company details such as contact information, billing details, or other company-specific data within your workflow automation. For example, you might update a company's address or status based on external triggers or data changes.

Use Case Examples

  1. Updating a company's billing address after receiving updated information from a CRM system.
  2. Modifying company contact details when a customer updates their profile through a web form.

Properties

Name Meaning
Company ID The unique identifier of the company to update. This is required to specify which company record to modify.
Dry Run If enabled, the node returns a preview of the update request without actually executing it. Useful for testing and validation to ensure the update payload is correct before making changes.
Impersonation Resource ID Optional resource ID to impersonate for write requests. If set, the update will be performed as this resource instead of the credential user.
Proceed Without Impersonation If Denied If impersonation is denied, this option allows retrying the update without impersonation, proceeding as the API user instead.
Fields The specific fields and values to update on the company record. This uses a resource mapper to define which company fields to modify and their new values.

Output

JSON

  • id - The unique identifier of the updated company.
  • name - The name of the updated company.
  • status - The status of the company after the update.
  • updatedFields - Details of the fields that were updated in the company record.

Dependencies

  • Requires an API key credential for Kaseya Autotask PSA REST API authentication.

Troubleshooting

  • Ensure the Company ID is correct and exists in the Autotask system to avoid 'not found' errors.
  • If using impersonation, verify the impersonation resource ID is valid and has write permissions.
  • When Dry Run is enabled, no changes are made; disable it to apply updates.
  • Check API rate limits and authentication credentials if requests fail.

Links

Discussion