Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node operation retrieves detailed information about a specific Project Charge from the Autotask system using its unique Charge ID. It is useful for workflows that need to fetch billing or charge details related to projects, such as financial reporting, invoicing automation, or project cost tracking. For example, a user can input a Charge ID to get all associated data fields, optionally including human-readable labels for picklist and reference fields, and flatten user-defined fields for easier access.

Properties

Name Meaning
Charge ID The unique identifier of the project charge to retrieve.
Add Picklist Labels Determines whether to add additional fields with human-readable labels for picklist fields in the response. Labels are only added if the picklist value is not empty.
Add Reference Labels Determines whether to add additional fields with human-readable labels for reference fields in the response. Labels are only added if the reference value is not empty.
Select Columns Names or IDs. Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields If enabled, user-defined fields (UDFs) are moved to the top level of the returned object instead of being nested inside a userDefinedFields array.

Output

JSON

  • id - The unique identifier of the project charge.
  • chargeDetails - Various fields describing the project charge, including amounts, dates, and related project information.
  • picklistLabels - Optional additional fields with human-readable labels for picklist fields, if enabled.
  • referenceLabels - Optional additional fields with human-readable labels for reference fields, if enabled.
  • userDefinedFields - Array of user-defined fields related to the project charge, unless flattened to top-level properties.

Dependencies

  • Requires an Autotask API key credential for authentication to access the Autotask REST API.

Troubleshooting

  • If the Charge ID is invalid or does not exist, the node will throw an error indicating the charge could not be found. Verify the Charge ID is correct.
  • If API authentication fails, ensure the Autotask API key credential is correctly configured and has sufficient permissions.
  • Selecting specific columns that do not exist or are misspelled may result in incomplete data or errors. Use the provided dropdown or expressions to select valid fields.
  • Enabling picklist or reference labels when the fields are empty will not add label fields; this is expected behavior.
  • Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields; disable flattening if this occurs.

Links

Discussion