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 company location records from the Autotask REST API using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter company locations, control the number of records returned, and customize the output fields. This is useful for scenarios where precise data extraction of company locations is needed, such as generating reports, syncing location data with other systems, or performing bulk data analysis.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching company location records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of company location 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 query criteria according to the Autotask API's advanced query syntax. This allows for complex filtering of company location records. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix for picklist fields to provide human-readable values alongside the raw data. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix for reference fields to provide human-readable values alongside the raw data. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If no fields are selected, all fields are returned by default. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are promoted to top-level properties in each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the company location record.name- Name of the company location.address- Address details of the company location.userDefinedFields- Array of user-defined fields associated with the company location, unless flattened.
_label - Human-readable label for picklist fields if 'Add Picklist Labels' is enabled._label - Human-readable label for reference fields if 'Add Reference Labels' is enabled.
Dependencies
- Requires an Autotask API key credential for authentication.
- Relies on the Autotask REST API endpoint for company locations.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is well-formed 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 in the response.
- If picklist or reference labels are not appearing, verify that the corresponding boolean properties are enabled and that the fields contain values.
- API rate limits or authentication errors may occur if the Autotask API key is invalid or overused. Check credentials and usage limits.
Links
- Autotask API Basic Query Calls - Official documentation for constructing advanced filter queries for Autotask API.