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 perform various operations on the Product Vendor resource, including counting the number of product vendors that match specified criteria. It is useful for workflows that need to retrieve aggregate data about product vendors, such as reporting the total number of vendors or filtering vendors based on certain fields. For example, a user can count how many product vendors exist with a specific attribute or status.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields to map or filter on when performing operations like count on the Product Vendor resource. This property allows users to specify the exact fields to include or use in the operation. |
Output
JSON
count- The total number of product vendors matching the specified criteria.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the node throws an error indicating the resource is not supported, verify that the resource parameter is set to 'productVendor'.
- Errors related to authentication usually mean the API key credential is missing or invalid; ensure correct credentials are configured.
- If the count result is zero unexpectedly, check the fields mapping and filters to ensure they match existing product vendor data.
- Network or API errors may occur if the Autotask API endpoint is unreachable; verify network connectivity and API availability.