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 enables users to create a Contract Ticket Purchase record in the Autotask system via its REST API. It is useful for automating the creation of ticket purchase entries related to contracts, which can help in managing contract-related ticketing activities efficiently. For example, a user can automate the purchase of tickets for a contract when certain conditions are met in their workflow, streamlining contract management and billing processes.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the specific fields and their values to map when creating or updating a Contract Ticket Purchase record. This property uses a resource mapper to allow users to specify which fields to include and how to map them from input data. |
Output
JSON
id- The unique identifier of the created Contract Ticket Purchase record.fields- An object containing the details of the Contract Ticket Purchase 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 'contractTicketPurchase' and the operation to 'create'.
- Errors related to authentication usually mean the Autotask API credentials are missing, invalid, or expired. Recheck and update the credentials in the node settings.
- Mapping errors can occur if required fields are missing or incorrectly mapped in the 'Fields' property. Ensure all mandatory fields for creating a Contract Ticket Purchase are provided.
- API rate limits or network issues can cause request failures. Check network connectivity and Autotask API usage limits.