Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node operation retrieves multiple Configuration Item Webhook records from the Autotask system. It is useful for scenarios where you need to fetch a list of configuration item webhooks, for example, to monitor webhook configurations, audit webhook setups, or integrate webhook data into other workflows. The operation supports fetching all records or limiting the number of records returned, and allows mapping specific fields to customize the output.

Properties

Name Meaning
Fields Defines which fields of the Configuration Item Webhook records to retrieve and map in the output. Supports auto-mapping and selective field inclusion.
Get All Determines whether to return all available Configuration Item Webhook records or limit the results to a specified maximum number.
Max Records Specifies the maximum number of Configuration Item 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, enhancing readability.
Add Reference Labels If enabled, adds 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 by choosing from a list or specifying field IDs via expressions. If none 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 record instead of being nested inside a userDefinedFields array, simplifying access.

Output

JSON

  • configurationItemWebhooks - Array of Configuration Item Webhook objects matching the query with fields as specified by the input properties.

Dependencies

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

Troubleshooting

  • If no records are returned, verify that the Configuration Item Webhooks exist and that the API credentials have sufficient permissions.
  • If the node fails with authentication errors, check that the Autotask API key credential is correctly configured and valid.
  • When selecting specific fields, ensure the field names or IDs are valid; invalid fields may cause errors or missing data.
  • If the 'Max Records' value is set outside the allowed range (1-500), the node may throw an error; adjust accordingly.

Discussion