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 'Get Many (Advanced)' operation for the 'Service Call' resource in the Autotask node allows users to retrieve multiple service call records from the Autotask REST API using advanced filtering criteria. This operation is beneficial when users need to query service calls with complex conditions beyond simple filters, enabling precise data retrieval. For example, a user can fetch all service calls that meet specific status, priority, or date range criteria by providing a JSON filter array. It supports returning all matching records or limiting the number of results, and can enhance the output by adding human-readable labels for picklist and reference fields, as well as flattening user-defined fields for easier access.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching service call records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of service call 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 service calls. This allows complex queries using Autotask's REST API filtering syntax. |
| Add Picklist Labels | Indicates whether to automatically add '_label' fields to picklist fields in the output, providing human-readable values for those fields. |
| Add Reference Labels | Indicates whether to automatically add '_label' fields to reference fields in the output, providing human-readable values for those fields. |
| Select Columns Names or IDs. | Allows selection of specific fields (columns) to include in the response. If no fields are selected, all fields are returned. The ID field is always included regardless of selection. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) are brought up to the top level of each returned object instead of being nested inside a 'userDefinedFields' array. |
Output
JSON
id- Unique identifier of the service call record.fields*- Selected fields of the service call record as per the 'Select Columns' input; includes all fields if none selected.*_label- Human-readable labels for picklist and reference fields, added if respective options are enabled.
userDefinedFields- Array of user-defined fields, unless 'Flatten User-Defined Fields' is enabled, in which case these fields appear at the top level.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' will cause the node to fail. Ensure the JSON string is correctly formatted and follows Autotask API filter syntax.
- Requesting too many records without 'Get All' enabled may result in incomplete data. Use 'Get All' to retrieve all matching records if needed.
- Selecting invalid or non-existent fields in 'Select Columns' may cause errors or missing data. Use 'Get Field Info' to verify field names.
- If labels are not appearing, verify that 'Add Picklist Labels' and 'Add Reference Labels' options are enabled and that the fields have valid values.
- Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields; disable flattening if this occurs.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct filter queries for API calls.