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 retrieve details about a specific Contract Ticket Purchase by its ID. It is useful for workflows that need to fetch detailed information about ticket purchases linked to contracts, such as billing, auditing, or reporting scenarios. For example, a user can automate the retrieval of contract ticket purchase data to update a CRM system or generate invoices.
Properties
| Name | Meaning |
|---|---|
| Contract Ticket Purchase ID | The unique identifier of the contract ticket purchase to retrieve. |
| Add Picklist Labels | Determines whether to add human-readable '_label' fields for picklist fields in the response, enhancing readability. |
| Add Reference Labels | Determines whether to add human-readable '_label' fields for reference fields in the response. |
| Select Columns Names or IDs. | Specifies which fields to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | Determines whether user-defined fields (UDFs) are promoted to top-level properties instead of being nested inside a userDefinedFields array. |
Output
JSON
id- The unique identifier of the contract ticket purchase.fields*- Selected fields of the contract ticket purchase, including standard and user-defined fields.
*_label- Human-readable labels for picklist and reference fields, if enabled.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the node returns an error indicating the contract ticket purchase ID is invalid or not found, verify that the provided ID exists and is correct.
- If no data is returned, check that the API credentials have sufficient permissions to access contract ticket purchase data.
- Errors related to missing fields may occur if selected columns do not exist; ensure selected fields are valid for the resource.
- Network or authentication errors may occur if the API key is invalid or the Autotask API endpoint is unreachable.