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 detailed information about a specific company location from the Autotask system using its unique Company Location ID. It is useful for workflows that need to fetch and utilize company location data, such as address details, contact information, or other location-specific attributes. For example, it can be used to integrate company location data into CRM systems, generate reports, or trigger location-based automation.
Properties
| Name | Meaning |
|---|---|
| Company Location ID | The unique identifier of the company location to retrieve information for. This is a required input to specify which company location record to fetch. |
| Add Picklist Labels | Determines whether to automatically add human-readable '_label' fields for picklist fields in the response. This helps interpret picklist values by providing their labels alongside raw values. |
| Add Reference Labels | Determines whether to automatically add human-readable '_label' fields for reference fields in the response. This provides readable labels for referenced entities. |
| Select Columns Names or IDs. | Allows selection of specific fields 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) should be brought up to the top level of the returned object instead of being nested inside a userDefinedFields array. This simplifies access to UDFs. |
Output
JSON
id- The unique identifier of the company location.name- The name of the company location.address- The address details of the company location.phone- Contact phone number for the company location.email- Contact email address for the company location.picklistField_label- Human-readable label for picklist fields if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable label for reference fields if 'Add Reference Labels' is enabled.userDefinedFields- Array of user-defined fields associated with the company location, unless flattened.userDefinedFieldName- User-defined fields brought to top-level properties if 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the Company Location ID is invalid or does not exist, the node will throw an error indicating the resource was not found. Verify the ID is correct.
- If API authentication fails, ensure the API key credential is correctly configured and has sufficient permissions.
- Selecting specific columns that do not exist may result in incomplete data or errors. Use the 'Select Columns' dropdown to choose valid fields.
- Enabling 'Add Picklist Labels' or 'Add Reference Labels' may increase response size and processing time; disable if not needed.
- If user-defined fields are not appearing as expected, check the 'Flatten User-Defined Fields' option to control their structure.