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
The 'Ticket Webhook - Get Many' operation in this node retrieves multiple ticket webhook records from the Autotask REST API. It allows users to fetch a list of ticket webhook entries with control over which fields to include, how many records to return, and whether to include human-readable labels for picklist and reference fields. This operation is useful for scenarios where you need to process or analyze multiple ticket webhook events, such as monitoring ticket updates or integrating ticket webhook data into other systems.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the ticket webhook records to retrieve and map. Supports custom mapping and auto-mapping of fields. |
| Get All | Boolean flag to determine whether to return all available ticket webhook records or limit the number of records returned. |
| Max Records | Specifies the maximum number of ticket webhook records to return when 'Get All' is false. The value can range from 1 to 500. |
| Add Picklist Labels | Determines whether to automatically add additional fields with '_label' suffix for picklist fields, providing human-readable values instead of raw codes. |
| Add Reference Labels | Determines whether to automatically add additional fields with '_label' suffix for reference fields, providing human-readable values. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response by choosing from a list or specifying field IDs via expressions. If no fields are selected, all fields are returned. The ID field is always included. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are brought to the top level of each returned object instead of being nested inside a 'userDefinedFields' array. |
Output
JSON
id- Unique identifier of the ticket webhook record.fields- The selected fields of the ticket webhook record as specified by the 'Fields' property.*_label- Additional fields with '_label' suffix providing human-readable labels for picklist and reference fields if enabled.userDefinedFields- Array of user-defined fields associated with the ticket webhook record, unless flattened to top-level properties.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If no records are returned, verify that the Autotask API credentials are correct and have sufficient permissions.
- Ensure that the 'Max Records' value is within the allowed range (1-500) when 'Get All' is false.
- If expected fields are missing, check the 'Fields' and 'Select Columns' settings to confirm the correct fields are selected.
- Network or API errors may occur if the Autotask service is unavailable or if rate limits are exceeded; retry after some time or check API usage.