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 records from the Autotask REST API using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter companies according to their needs. The node supports returning all matching records or limiting the number of results, and can enhance output by adding human-readable labels for picklist and reference fields. It also offers options to select specific columns and flatten user-defined fields for easier access. This operation is useful for scenarios where detailed and customized company data retrieval is required, such as generating reports, syncing data with other systems, or performing bulk data analysis.
Properties
| Name | Meaning |
|---|---|
| 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. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array with Autotask API query criteria to filter the company records. |
| Add Picklist Labels | Indicates whether to automatically add '_label' fields for picklist fields to provide human-readable values in the output. |
| Add Reference Labels | Indicates whether to automatically add '_label' fields for reference fields to provide human-readable values in the output. |
| 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. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) are brought up to the top level of each company object instead of being nested inside the userDefinedFields array. |
Output
JSON
id- Unique identifier of the company record.name- Name of the company.picklistField_label- Human-readable label for a picklist field, added if 'Add Picklist Labels' is true.referenceField_label- Human-readable label for a reference field, added if 'Add Reference Labels' is true.userDefinedFields- User-defined fields nested inside the userDefinedFields array, or at top-level if 'Flatten User-Defined Fields' is true. - Other selected fields as specified by the 'Select Columns' property.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests to the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause parsing errors. Ensure the JSON string is well-formed and follows Autotask API query criteria format.
- Requesting too many records without pagination or limits may lead to timeouts or API rate limiting. Use 'Get All' carefully or set reasonable 'Max Records'.
- Selecting invalid or non-existent columns in 'Select Columns' may result in incomplete or error responses. Use 'Get Field Info' to verify field names.
- If human-readable labels are not appearing, verify that 'Add Picklist Labels' and 'Add Reference Labels' are enabled and that the fields have valid values.
- API authentication errors indicate invalid or missing credentials. Check the Autotask API credential configuration in n8n.
Links
- Autotask API Basic Query Calls - Official Autotask API documentation describing query filters and usage.
- n8n Expressions Documentation - Guide on using expressions in n8n, useful for dynamic field selection.