Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

The 'Ticket Webhook' resource with the 'Get Many (Advanced)' operation allows users to retrieve multiple ticket webhook records from the Autotask system using advanced filtering criteria. This operation is beneficial when you need to query ticket webhook data with complex conditions, such as filtering by specific fields or values, and control the number of records returned. For example, you can fetch all ticket webhooks created within a date range or those matching certain status codes, enabling detailed data analysis or integration workflows.

Properties

Name Meaning
Get All Determines whether to return all matching ticket webhook records or limit the results to a specified maximum number.
Max Records Specifies the maximum number of ticket webhook 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 apply complex filtering on ticket webhook records.
Add Picklist Labels Indicates whether to automatically add human-readable '_label' fields for picklist fields in the output, enhancing readability.
Add Reference Labels Indicates 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 no fields are selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields Determines whether user-defined fields (UDFs) should be promoted to top-level properties in each returned object instead of being nested.

Output

JSON

  • id - Unique identifier of the ticket webhook record.
  • fieldName - Various fields of the ticket 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.

Dependencies

  • Requires an Autotask API credential (API key or token) for authentication.
  • Relies on the Autotask REST API to fetch ticket webhook data.

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 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 match existing ticket webhook data.
  • Authentication errors may occur if the Autotask API credentials are missing or invalid; verify credentials configuration.
  • Selecting fields that do not exist or are misspelled in 'Select Columns' may result in incomplete data or errors.

Links

Discussion