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 retrieves multiple company location records from the Autotask REST API. It is useful for scenarios where you need to fetch a list of company locations, such as for reporting, synchronization with other systems, or bulk data processing. For example, you can use it to get all locations of a company to update an internal database or to display location options in a user interface.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the company location records to retrieve and map in the output. Supports custom mapping and selection of specific fields. |
| Get All | Determines whether to return all matching company location records or limit the number of records returned. |
| Max Records | Specifies the maximum number of company location records to return when 'Get All' is false. The value can range from 1 to 500. |
| Add Picklist Labels | If enabled, adds additional fields with human-readable labels for picklist fields in the output, improving readability. |
| Add Reference Labels | If enabled, adds additional fields with human-readable labels for reference fields in the output. |
| Select Columns Names or IDs. | Allows selection of specific columns (fields) to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought to the top level of each record object instead of being nested inside a userDefinedFields array, simplifying access. |
Output
JSON
id- Unique identifier of the company location record.name- Name of the company location.address- Address details of the company location.phone- Phone number associated with the location.userDefinedFields- Array of user-defined fields related to the company location, if not flattened.
_label - Human-readable labels for picklist or reference fields, added if enabled in the input properties.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the node returns no data, verify that the company has locations and that the API credentials have sufficient permissions.
- If the node times out or returns an error, check network connectivity and API rate limits.
- Ensure that the 'Max Records' value is within the allowed range (1-500) when 'Get All' is false.
- If picklist or reference labels are missing, confirm that the corresponding input properties 'Add Picklist Labels' and 'Add Reference Labels' are enabled.