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 operation retrieves multiple Ticket Note records from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter the ticket notes returned. This is useful for scenarios where you need to extract specific ticket notes based on detailed conditions, such as notes created within a date range, by certain users, or containing specific content. For example, a support manager might use this to gather all ticket notes related to a particular issue type or customer for reporting or analysis.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching ticket note records or limit the number of results. |
| Max Records | Specifies the maximum number of ticket note records to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A JSON string containing a 'filter' array with Autotask API query criteria to filter the ticket notes. This allows for complex and precise queries. |
| Add Picklist Labels | If enabled, adds human-readable '_label' fields for picklist fields in the output, improving readability. |
| Add Reference Labels | If enabled, adds human-readable '_label' fields for reference fields in the output. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response. If none are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are moved to the top level of each returned object instead of being nested, simplifying access. |
Output
JSON
id- Unique identifier of the ticket note.content- The text content of the ticket note.createdDate- Date and time when the ticket note was created.createdByResourceID- Identifier of the resource (user) who created the note.ticketID- Identifier of the ticket to which this note belongs.picklistField_label- Human-readable label for picklist fields, if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable label for reference fields, if 'Add Reference Labels' is enabled.userDefinedFields- User-defined custom fields, either nested or flattened to top-level depending on 'Flatten User-Defined Fields' setting.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is correctly formatted and follows Autotask API filter syntax.
- Requesting too many records without pagination or 'Get All' enabled may lead to timeouts or API limits being hit.
- Selecting fields that do not exist or are misspelled in 'Select Columns' can cause errors or missing data.
- If picklist or reference labels are not appearing, verify that the corresponding options are enabled and that the fields contain values.
- API authentication errors may occur if the API key credential is missing, expired, or incorrect.
Links
- Autotask API Basic Query Calls - Official Autotask documentation on constructing API queries and filters.