Autotask icon

Autotask

Consume Autotask REST API

Actions389

Overview

This node operation retrieves multiple Contact Webhook records from the Autotask system. It is useful for scenarios where you need to fetch a list of contact webhook configurations, for example, to synchronize webhook settings, audit webhook usage, or integrate webhook data into other workflows. Users can specify which fields to retrieve, limit the number of records, and control how picklist and reference fields are labeled for easier interpretation.

Properties

Name Meaning
Fields Defines which fields of the Contact Webhook resource to retrieve and map in the output. Supports custom mapping and selection of specific fields.
Get All Determines whether to return all available Contact Webhook records or limit the results to a specified maximum number.
Max Records Specifies the maximum number of Contact Webhook records to return when 'Get All' is false. Value range is 1 to 500.
Add Picklist Labels If enabled, adds human-readable label fields for picklist fields in the output, making it easier to understand picklist values.
Add Reference Labels If enabled, adds human-readable label fields for reference fields in the output, improving readability of referenced data.
Select Columns Names or IDs. Allows selection of specific columns (fields) to include in the response. If none are selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields When enabled, user-defined fields (UDFs) are promoted to top-level properties in each returned object instead of being nested inside a userDefinedFields array.

Output

JSON

  • id - Unique identifier of the Contact Webhook record.
  • fieldName
    • _label - Human-readable labels for picklist or reference fields if Add Picklist Labels or Add Reference Labels is enabled.
  • userDefinedFields
    • udfName - User-defined fields nested or flattened depending on Flatten User-Defined Fields setting.

Dependencies

  • Requires an API key credential for Autotask REST API authentication.

Troubleshooting

  • If no records are returned, verify that the Contact Webhook resource exists and that the API credentials have sufficient permissions.
  • Errors related to field mapping may occur if specified fields do not exist; ensure correct field names or IDs are used.
  • If the node returns partial data, check the Max Records setting and the Get All flag to ensure the desired number of records is fetched.

Discussion