Actions524
- AI Helper Actions
- Tool Actions
- API Threshold Actions
- Appointment Actions
- Billing Code Actions
- Billing Items Actions
- Change Request Link Actions
- Checklist Library Actions
- Checklist Library Item Actions
- Classification Icon Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Company Site Configuration Actions
- Configuration Item Actions
- Configuration Item Billing Product Association 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
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Contract Exclusion Billing Code 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 Rate Actions
- Contract Role Costs Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Department Actions
- Project Phase Actions
- Quote Item Actions
- Quote Location Actions
- Quote Template Actions
- Resource Actions
- Resource Role Actions
- Resource Role Queue Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Subscription Actions
- Subscription Period Actions
- Ticket Category Actions
- Ticket Category Field Default Actions
- Ticket History Actions
- Ticket Note Actions
Company → Get Many
AI-generatedOverview
This node operation retrieves multiple company records from the Autotask PSA system. It supports fetching all records or limiting the number of records returned, with options to customize the output fields and format. This operation is useful for scenarios where you need to list or analyze multiple companies, such as generating reports, syncing company data with other systems, or performing bulk updates.
Use Case Examples
- Fetch all companies to synchronize with a CRM system.
- Retrieve a limited number of company records for display in a dashboard.
- Get company data with human-readable labels for picklist and reference fields for easier interpretation.
Properties
| Name | Meaning |
|---|---|
| Get All | Whether to return all company records or only up to a specified limit. |
| Max Records | Maximum number of company records to return when not returning all. Range is 1 to 500. |
| Add Picklist Labels | Automatically add "_label" fields for picklist fields with human-readable values, excluding empty values. |
| Add Reference Labels | Automatically add "_label" fields for reference fields with human-readable values, excluding empty values. |
| Select Columns Names or IDs. | Choose which company fields to include in the response. If none selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Bring user-defined fields (UDFs) up to the top level of each company object instead of nested inside the userDefinedFields array. |
| Fields | Define or map specific company fields to be included or manipulated in the operation. |
Output
JSON
id- Unique identifier of the company record.name- Name of the company.address- Company address details.phone- Company phone number.email- Company email address._label- Human-readable labels for picklist or reference fields if enabled.userDefinedFields- Array of user-defined fields associated with the company, or flattened to top-level properties if enabled.
Dependencies
- An API key credential for Autotask PSA REST API authentication.
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access company data.
- If the node returns no data, verify that the company records exist and the query parameters (like max records) are set appropriately.
- Errors related to rate limits may occur; ensure the API usage complies with Autotask's rate limits and retry accordingly.
Links
- Autotask PSA REST API Documentation - Official documentation for Autotask PSA REST API endpoints and usage.