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
The node builds search filter groups for querying the Autotask API. It allows users to define complex logical filter groups with multiple conditions, combining them using AND/OR operators. This is useful for constructing precise queries to retrieve data from Autotask based on specific field values, including user-defined fields (UDFs). For example, a user can build a filter to find tickets where the status equals 'Open' and the priority is greater than 2.
Properties
| Name | Meaning |
|---|---|
| Filter Groups | Defines one or more groups of filter conditions combined by a logical operator (AND/OR). Each group contains multiple conditions specifying field names, operators, value types, and values to filter Autotask API queries. |
Output
JSON
filterGroups- An array representing the constructed filter groups with their logical operators and conditions, formatted for Autotask API queries.
Dependencies
- Requires an Autotask API credential for authentication.
Troubleshooting
- Ensure only one user-defined field (UDF) is used per query as per Autotask API limitations; using multiple UDFs may cause errors.
- Verify that field names and operators are valid and supported by the Autotask API to avoid query failures.
- Date values must be correctly formatted and timezone-aware if applicable to prevent incorrect filtering results.
- Boolean values should be specified as true or false strings or boolean types to match API expectations.
Links
- Autotask API Filter Documentation - Official documentation on how to construct filters for Autotask API queries.