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 update an existing product record. It allows users to specify the product by its ID and update various fields of the product using a flexible field mapping mechanism. This is useful in scenarios where product information needs to be programmatically updated in Autotask, such as syncing product data from another system or automating product updates based on business logic.
Properties
| Name | Meaning |
|---|---|
| Product ID | The unique identifier of the product to update. This is required to specify which product record will be modified. |
| Fields | A resource mapper input that defines which product fields to update and their new values. It supports defining fields manually or using auto-mapping features to specify the update data. |
Output
JSON
id- The ID of the updated product.fields- The updated fields and their new values returned from the Autotask API.
Dependencies
- Requires an Autotask API credential for authentication to access the Autotask REST API.
Troubleshooting
- Ensure the Product ID provided exists in Autotask; otherwise, the update will fail with a not found error.
- Verify that the fields specified in the Fields property are valid and allowed to be updated for the product resource.
- Authentication errors may occur if the Autotask API credentials are missing or invalid; reconfigure credentials if needed.
- If the API rate limits are exceeded, the node may throw errors; consider adding delays or retries in your workflow.