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 Webhook records from the Autotask REST API using advanced filtering criteria. It is useful for scenarios where users need to query and extract specific webhook data related to ticket notes, applying complex filters to narrow down results. For example, a user might want to fetch all ticket note webhooks created within a certain date range or matching particular status codes.
Properties
| Name | Meaning |
|---|---|
| Get All | Determines whether to return all matching records or limit the number of results. |
| Max Records | Specifies the maximum number of records to return when 'Get All' is false. The value must be between 1 and 500. |
| Advanced Filter | A required JSON string containing a 'filter' array with Autotask API query criteria to filter the ticket note webhook records. |
| Add Picklist Labels | Whether to automatically add human-readable '_label' fields for picklist fields in the output. |
| Add Reference Labels | Whether to automatically add 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 | Whether to bring user-defined fields (UDFs) to the top level of each returned object instead of nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the ticket note webhook record.fieldName- Various fields of the ticket note webhook record as returned by the Autotask API, including standard and user-defined fields._label- Optional human-readable labels for picklist and reference fields if enabled.userDefinedFields- Array of user-defined fields unless flattened to top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in the 'Advanced Filter' property will cause errors. Ensure the JSON string is well-formed and follows the Autotask API filter structure.
- Requesting more than 500 records when 'Get All' is false will be limited to 500 due to API constraints.
- If no records are returned, verify that the filter criteria correctly match existing ticket note webhook records.
- Errors related to authentication indicate missing or invalid API credentials; verify the Autotask API key is correctly configured.
- Selecting invalid or unsupported fields in 'Select Columns' may cause API errors; use 'Get Field Info' to confirm valid field names.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct filter queries for API calls.