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 Vendor records from the Autotask system. It is useful for scenarios where you need to fetch a list of vendors associated with products, such as for inventory management, vendor analysis, or integration with other systems. For example, you can use it to get all product vendors or a limited number of them, optionally mapping specific fields and including human-readable labels for picklist and reference fields.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Product Vendor resource to retrieve and map in the output. Supports custom mapping and auto-mapping of fields. |
| Get All | Boolean flag to determine whether to return all matching Product Vendor records or limit the number of records returned. |
| Max Records | Specifies the maximum number of Product Vendor records to return when 'Get All' is false. The value must be between 1 and 500. |
| Add Picklist Labels | Determines whether to add additional fields with human-readable labels for picklist fields in the output. Labels are added only for non-empty values. |
| Add Reference Labels | Determines whether to add additional fields with human-readable labels for reference fields in the output. Labels are added only for non-empty values. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response by choosing from a list or specifying field IDs via expressions. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the Product Vendor record.name- Name of the Product Vendor.fieldsToMap*- Mapped fields as specified by the 'Fields' property, containing the selected data for each Product Vendor.
*_label- Optional human-readable labels for picklist and reference fields, added if enabled in the node properties.userDefinedFields*- User-defined fields either nested or flattened to top-level properties depending on the 'Flatten User-Defined Fields' setting.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the Product Vendor data exists in the Autotask system and that the API credentials have sufficient permissions.
- If the node returns an error about unsupported resource, ensure the 'Resource' parameter is set to 'productVendor'.
- When selecting specific fields, ensure the field IDs or names are valid; otherwise, the output may be incomplete or cause errors.
- If the node times out or returns partial data, consider enabling 'Get All' to retrieve all records or increasing the 'Max Records' limit within allowed bounds.
- Errors related to API authentication usually indicate invalid or missing API credentials; verify and update the credentials accordingly.