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 integrates with the Autotask REST API to manage Product Vendor entities. Specifically, the 'Create' operation for the 'Product Vendor' resource allows users to add new product vendors into their Autotask system. This is useful for automating vendor management workflows, such as adding new suppliers or partners programmatically. For example, a user can create a new product vendor by mapping relevant fields like vendor name, contact details, and other attributes, enabling seamless synchronization between Autotask and other systems.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the fields and their values to map when creating or updating a Product Vendor. This property uses a resource mapper to specify which fields to include and their corresponding values. |
Output
JSON
id- The unique identifier of the created Product Vendor.name- The name of the Product Vendor.fields- An object containing the mapped fields and their values as returned by the Autotask API after creation.
Dependencies
- Requires an Autotask API credential (API key or token) to authenticate requests to the Autotask REST API.
Troubleshooting
- If the node throws an error indicating unsupported resource or operation, verify that the 'resource' is set to 'productVendor' and the 'operation' is set to 'create'.
- Errors related to missing or invalid fields may occur if required fields are not mapped correctly in the 'Fields' property. Ensure all mandatory fields for creating a Product Vendor in Autotask are provided.
- Authentication errors may occur if the Autotask API credentials are missing, expired, or incorrect. Verify and update the credentials in the node settings.
- Network or API errors can happen if the Autotask service is unreachable or returns an error. Check network connectivity and Autotask service status.