Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

The node interacts with the Autotask API to retrieve details about a specific Ticket Webhook by its ID. It supports fetching a single webhook's data, optionally enhancing the output with human-readable labels for picklist and reference fields, selecting specific fields to return, and flattening user-defined fields for easier access. This is useful for automation workflows that need to monitor or process ticket webhook configurations in Autotask, such as syncing webhook settings or auditing webhook details.

Properties

Name Meaning
Webhook ID The unique identifier of the ticket webhook to retrieve.
Add Picklist Labels Whether to add additional fields with human-readable labels for picklist fields in the response.
Add Reference Labels Whether to add additional fields with human-readable labels for reference fields in the response.
Select Columns Names or IDs. Specify which fields to include in the response. If none selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields Whether to move user-defined fields from nested arrays to top-level properties in the output for easier access.

Output

JSON

  • id - The unique identifier of the ticket webhook.
  • fieldName
    • _label - Human-readable labels for picklist or reference fields if enabled.
  • userDefinedFields
    • fieldName
      * or
      * fieldName - User-defined fields either nested or flattened to top-level depending on configuration.

Dependencies

  • Requires an Autotask API credential for authentication to access the Autotask REST API.

Troubleshooting

  • Ensure the provided Webhook ID exists and is accessible with the given API credentials; otherwise, the node will return an error indicating the webhook was not found.
  • If no fields are returned, verify that the 'Select Columns' property is correctly set or left empty to fetch all fields.
  • If labels for picklist or reference fields are missing, check that the corresponding boolean properties ('Add Picklist Labels' and 'Add Reference Labels') are enabled.
  • Flattening user-defined fields may cause naming conflicts if UDF names overlap with standard fields; disable flattening if unexpected data structure issues occur.

Discussion