Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node operation retrieves multiple Project Phase records from the Autotask system. It is useful for workflows that need to fetch and process lists of project phases, such as reporting on project progress, synchronizing project data with other systems, or automating project management tasks. For example, a user can fetch all project phases related to a specific project to analyze timelines or update statuses in bulk.

Properties

Name Meaning
Fields Defines which fields of the Project Phase 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 Phase records or limit the number of records returned.
Max Records Specifies the maximum number of Project Phase records to return when 'Get All' is false. The value must be between 1 and 500.
Add Picklist Labels If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the output.
Add Reference Labels If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the output.
Select Columns Names or IDs. Allows selection of specific fields (columns) to include in the response. If none 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 each returned object instead of being nested inside a userDefinedFields array.

Output

JSON

  • id - Unique identifier of the project phase.
  • name - Name of the project phase.
  • startDate - Start date of the project phase.
  • endDate - End date of the project phase.
  • status - Status of the project phase.
  • userDefinedFields - Array of user-defined fields associated with the project phase, unless flattened.
  • *_label - Additional fields with '_label' suffix provide human-readable labels for picklist or reference fields if enabled.

Dependencies

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

Troubleshooting

  • If no records are returned, verify that the project phases exist and that the API credentials have sufficient permissions.
  • If the node returns an error about unsupported resource, ensure the resource parameter is set to 'phase'.
  • If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to retrieve all records.
  • If picklist or reference labels are missing, check that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled.
  • Errors related to field mapping may occur if selected fields do not exist; verify field names or IDs in the 'Fields' property.

Links

Discussion