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 updates an existing Contract Ticket Purchase record in the Autotask system. It is useful for scenarios where you need to modify details of a previously created contract ticket purchase, such as changing quantities, dates, or other relevant fields. For example, if a ticket purchase was initially recorded with incorrect information or needs adjustment due to changes in contract terms, this node allows you to update that record programmatically within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Contract Ticket Purchase ID | The unique identifier of the contract ticket purchase record to update. This is required to specify which record should be modified. |
| Fields | A resource mapper input that defines which fields of the contract ticket purchase should be updated and their new values. This allows selective updating of one or more fields based on the user's mapping configuration. |
Output
JSON
id- The unique identifier of the updated contract ticket purchase record.fields- The updated fields and their values after the update operation.status- The status or result of the update operation, indicating success or failure.
Dependencies
- Requires an Autotask API key credential for authentication to access and modify contract ticket purchase records via the Autotask REST API.
Troubleshooting
- If the Contract Ticket Purchase ID is missing or invalid, the node will fail to locate the record to update. Ensure the ID is correct and exists in Autotask.
- Incorrect or unsupported field mappings in the 'Fields' property may cause the update to fail. Verify that the fields being updated are valid and allowed to be modified.
- API authentication errors may occur if the Autotask API key credential is invalid or expired. Re-authenticate or update the credential as needed.
- Network or connectivity issues with the Autotask API endpoint can cause operation failures. Check network access and API availability.