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 tasks from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter tasks according to their needs. This is useful for scenarios where users need to extract a customized list of project tasks based on specific conditions, such as status, assigned resources, dates, or other task attributes. For example, a project manager could use this to get all tasks assigned to a particular team within a date range or all tasks with a certain priority level.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching project tasks or limit the number of results. |
| Max Records | Specifies the maximum number of project task 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 that defines the Autotask API query criteria to filter project tasks. This allows for complex and precise filtering based on Autotask's query syntax. |
| Add Picklist Labels | If enabled, adds human-readable '_label' fields for picklist fields in the output, making it easier to understand picklist values. |
| Add Reference Labels | If enabled, adds human-readable '_label' fields for reference fields in the output, improving readability of referenced entities. |
| 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 brought to the top level of each task object instead of being nested inside a userDefinedFields array, simplifying access. |
Output
JSON
id- Unique identifier of the project task.name- Name or title of the project task.status- Current status of the task.assignedResourceId- ID of the resource assigned to the task.assignedResourceId_label- Human-readable label for the assigned resource (if Add Reference Labels is enabled).priority- Priority level of the task.priority_label- Human-readable label for the priority picklist (if Add Picklist Labels is enabled).userDefinedFields- Individual user-defined field values if Flatten User-Defined Fields is enabled. - Additional fields selected via Select Columns or returned by default.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in the Advanced Filter property will cause errors. Ensure the JSON string is well-formed and follows Autotask API query syntax.
- Requesting too many records without pagination or limits may cause timeouts or API throttling.
- If no results are returned, verify that the filter criteria correctly match existing project tasks.
- Enabling Add Picklist Labels or Add Reference Labels requires that the referenced data is accessible; otherwise, labels may be missing.
- Selecting invalid or non-existent columns in Select Columns may cause errors or empty fields in the output.
Links
- Autotask API Basic Query Calls - Official Autotask documentation on how to construct query filters for API calls.