Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
This node operation retrieves multiple Project records from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter projects according to their needs. This is useful for scenarios where users need to extract a customized list of projects based on specific conditions, such as projects within a date range, with certain statuses, or matching other detailed attributes. For example, a project manager could use this to get all active projects assigned to a particular team or client.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching project records or limit the number of results. |
| Max Records | Specifies the maximum number of project records to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array with Autotask API query criteria to filter projects. This allows complex and precise filtering based on Autotask's REST API query syntax. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields in the project data. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields in the project data. |
| Select Columns Names or IDs. | Allows selection of specific project 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 each project object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the project.name- Name of the project.status- Current status of the project.userDefinedFields- Array of user-defined fields associated with the project, unless flattened.
- Other selected project fields as specified by the 'Select Columns' property._label - Human-readable labels for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' is enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is correctly formatted and follows Autotask API query syntax.
- Requesting too many records without 'Get All' enabled may result in incomplete data. Use 'Get All' carefully to avoid performance issues.
- Selecting fields that do not exist or are misspelled in 'Select Columns' may cause errors or missing data.
- If picklist or reference labels are not appearing, verify that the corresponding fields have valid values and that label addition options are enabled.
- API rate limits or authentication errors may occur if the Autotask API key is invalid or expired.
Links
- Autotask API Basic Query Calls - Official documentation for constructing advanced filter queries for Autotask REST API.