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 perform operations related to Contract Ticket Purchases, specifically supporting the 'Count' operation. It allows users to count the number of contract ticket purchase records that match specified criteria. This is useful for reporting, monitoring, or conditional workflows where the number of ticket purchases under contracts needs to be evaluated. For example, a user might count how many ticket purchases exist for a particular contract or within a date range to trigger alerts or further processing.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Contract Ticket Purchase resource to map or use in the operation. This property supports resource mapping with options to define fields manually or auto-map them, enabling precise control over the data involved in the count operation. |
Output
JSON
count- The total number of Contract Ticket Purchase records matching the specified criteria.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If the node throws an error indicating the resource is not supported, verify that the 'resource' parameter is set to 'contractTicketPurchase'.
- Authentication errors may occur if the Autotask API credentials are missing or invalid; ensure valid API credentials are configured.
- Incorrect or incomplete field mappings in the 'Fields' property may cause unexpected results or errors; verify the fields selected are valid for the Contract Ticket Purchase resource.
- Network or API rate limit issues can cause failures; check network connectivity and Autotask API usage limits.