Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

The node interacts with the Autotask REST API to retrieve multiple Project Charge records. It supports fetching either all available records or a limited number, with options to customize which fields are returned and how data is presented. This is useful for workflows that need to process or analyze billing charges associated with projects, such as generating reports, syncing data with other systems, or automating financial operations.

Properties

Name Meaning
Fields Defines which fields of the Project Charge resource to retrieve and map in the output. Supports custom mapping and auto-mapping of fields.
Get All Determines whether to return all matching Project Charge records or limit the number of records returned.
Max Records Specifies the maximum number of Project Charge records to return when 'Get All' is false. Value range is 1 to 500.
Add Picklist Labels If enabled, adds human-readable label fields for picklist fields in the output, enhancing readability.
Add Reference Labels If enabled, adds human-readable label fields for reference fields in the output.
Select Columns Names or IDs. Allows selection of specific fields to include in the response. If none selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields If enabled, user-defined fields (UDFs) are promoted to top-level properties in each record instead of being nested, simplifying access.

Output

JSON

  • id - Unique identifier of the Project Charge record.
    - Standard or user-defined fields of the Project Charge as specified by the 'Fields' property._label - Human-readable labels for picklist or reference fields if enabled.

Dependencies

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

Troubleshooting

  • If the node returns an error about unsupported resource, verify that 'Project Charge' is correctly selected as the resource.
  • Errors related to authentication usually indicate missing or invalid API credentials; ensure the Autotask API key is correctly configured.
  • If no records are returned, check that the Project Charge data exists in Autotask and that any filters or field selections are correct.
  • When selecting fields, ensure that the field IDs or names are valid for the Project Charge resource to avoid mapping errors.

Discussion