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 Service records from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter the services returned. Users can choose to return all matching records or limit the number of records returned. Additionally, it supports options to include human-readable labels for picklist and reference fields, select specific columns to return, and flatten user-defined fields for easier access. This operation is useful for scenarios where detailed and customized retrieval of service data is needed, such as generating reports, syncing service data with other systems, or performing bulk data analysis.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching service records or limit the results to a maximum number. |
| Max Records | Specifies the maximum number of service records to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to filter the service records returned. This allows complex and precise querying. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable values for picklist fields in the returned data. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable values for reference fields in the returned data. |
| 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. |
| Flatten User-Defined Fields | If enabled, 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 record.fieldName- Various service fields as specified by the selected columns or all fields if none selected.fieldName_label- Human-readable labels for picklist or reference fields if the respective options are enabled.userDefinedFields- Array of user-defined fields if flattening is disabled; otherwise, UDFs appear as top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property can cause query failures. Ensure the JSON is well-formed and follows Autotask API query criteria syntax.
- Requesting too many records without pagination or 'Get All' enabled may lead to timeouts or API limits being hit.
- Selecting invalid or non-existent columns in 'Select Columns' may result in errors or missing data.
- If picklist or reference labels are not appearing, verify that the respective options are enabled and that the fields actually have label data.
- Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields.
Links
- Autotask API Basic Query Calls - Official Autotask documentation on constructing API queries and filters.