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 interacts with the Autotask REST API to retrieve multiple company records based on user-defined criteria. It is useful for workflows that require bulk access to company data, such as generating reports, syncing company information with other systems, or performing batch updates. For example, a user can fetch all companies with specific fields mapped, limit the number of records returned, and include human-readable labels for picklist and reference fields.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which company fields to retrieve and map in the output. Supports auto-mapping and selective field inclusion. |
| Get All | Determines whether to return all matching company records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of company records to return when 'Get All' is false. Valid range is 1 to 500. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for picklist fields. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix containing human-readable labels for reference fields. |
| Select Columns Names or IDs. | Allows selection of specific company fields to include in the response. If none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are promoted to top-level properties instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the company record.fields- Mapped company fields as specified by the 'Fields' property._label - Human-readable labels for picklist or reference fields if enabled.userDefinedFields- Array of user-defined fields unless 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the API credentials are correct and have sufficient permissions.
- Ensure that the 'Fields' property is properly configured to include the desired fields; otherwise, the output may be incomplete.
- When 'Get All' is false, the 'Max Records' value must be between 1 and 500; values outside this range may cause errors.
- If picklist or reference labels are not appearing, check that the corresponding 'Add Picklist Labels' and 'Add Reference Labels' options are enabled.
- Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields; disable flattening if this occurs.