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 interacts with the Autotask REST API to retrieve multiple records of a specified resource using advanced filtering criteria. It is designed for scenarios where users need to query Autotask data with complex filters beyond simple retrieval, such as fetching resources that meet specific conditions or criteria. For example, a user can retrieve a filtered list of resources based on custom JSON filters, control the number of records returned, and optionally include human-readable labels for picklist and reference fields.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching results or limit the output to a specified maximum number of records. |
| Max Records | Specifies the maximum number of 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 for filtering the records. |
| Add Picklist Labels | Indicates whether to automatically add additional fields with '_label' suffix for picklist fields, providing human-readable values instead of raw codes. |
| Add Reference Labels | Indicates whether to automatically add additional fields with '_label' suffix for reference fields, providing human-readable values. |
| 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 | Determines whether user-defined fields (UDFs) should be moved to the top level of each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
- `` - An array of resource objects matching the advanced filter criteria. Each object contains the requested fields, including optional picklist and reference labels, and optionally flattened user-defined fields.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests to the Autotask REST API.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property will cause the node to fail. Ensure the JSON string is correctly formatted and contains a 'filter' array as per Autotask API documentation.
- Requesting more than 500 records when 'Get All' is false will be limited to 500 due to API constraints.
- If no records are returned, verify that the filter criteria correctly match existing data.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' may increase response size; disable if not needed.
- If user-defined fields are not appearing as expected, check the 'Flatten User-Defined Fields' setting.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct query filters for API calls.