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 Ticket Notes, specifically to count the number of ticket notes matching certain criteria. It is useful for workflows that need to retrieve the total count of ticket notes for reporting, monitoring, or conditional logic based on the number of notes associated with tickets. For example, a user might want to count all notes for a specific ticket or within a date range to trigger alerts or further processing.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the ticket notes to map or consider when performing the count operation. This property allows users to specify and map the relevant fields for the ticket note resource, supporting custom field selection and filtering. |
Output
JSON
count- The total number of ticket notes matching the specified criteria.
Dependencies
- Requires an API key credential for authenticating with the Autotask REST API.
Troubleshooting
- If the node throws an error indicating the resource is not supported, verify that the resource is set to 'ticketNote' and the operation to 'count'.
- Authentication errors may occur if the API key credential is missing or invalid; ensure the credential is correctly configured.
- Incorrect or incomplete field mappings in the 'Fields' property may cause unexpected results or errors; verify the field selections are valid for ticket notes.
- Network or API rate limit errors can occur; check network connectivity and Autotask API usage limits.