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 Product records from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter products, control the number of records returned, and customize the output fields. This is useful for scenarios where precise product data extraction is needed, such as generating reports, syncing product catalogs, or integrating product data with other systems.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching product records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of product 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 that defines the Autotask API query criteria to filter products. Users should construct this JSON using the Autotask API documentation and helper tools. |
| Add Picklist Labels | Indicates whether to automatically add human-readable '_label' fields for picklist fields in the product data. Empty values will not have labels added. |
| Add Reference Labels | Indicates whether to automatically add human-readable '_label' fields for reference fields in the product data. Empty values will not have labels added. |
| Select Columns Names or IDs. | Allows selection of specific product 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 product object instead of being nested inside a 'userDefinedFields' array. |
Output
JSON
id- Unique identifier of the product record.fields*- Various product fields as returned by the Autotask API, including standard and user-defined fields.
*_label- Optional human-readable labels for picklist and reference fields if enabled.
Dependencies
- Requires an Autotask API credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property can cause query failures. Ensure the JSON is well-formed and follows Autotask API filter syntax.
- Requesting too many records without 'Get All' enabled may result in incomplete data. Use 'Get All' to retrieve all matching records if needed.
- Selecting fields that do not exist or are misspelled in 'Select Columns' may cause errors or missing data.
- Network or authentication errors may occur if the Autotask API credentials are invalid or expired. Verify and update credentials as needed.
Links
- Autotask API Basic Query Calls - Official Autotask documentation for constructing API query filters.
- n8n Expressions Documentation - Guide on using expressions in n8n, useful for dynamic field selection.