Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node operation retrieves multiple Configuration Item DNS Record entries from the Autotask system using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter the DNS records returned. This is useful for scenarios where you need to fetch a customized subset of DNS records based on specific attributes or conditions, such as retrieving all DNS records related to a particular configuration item or matching certain DNS record types. For example, a user can fetch all DNS records with a specific domain name or those created within a certain date range.

Properties

Name Meaning
Get All Determines whether to return all matching DNS records or limit the number of records returned.
Max Records Specifies the maximum number of DNS records to return when 'Get All' is false. The value must be between 1 and 500.
Advanced Filter A required JSON string containing a 'filter' array that defines the query criteria for filtering DNS records according to the Autotask API query syntax.
Add Picklist Labels Indicates whether to add human-readable '_label' fields for picklist fields in the returned DNS records.
Add Reference Labels Indicates whether to add human-readable '_label' fields for reference fields in the returned DNS records.
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) are promoted to top-level properties in each DNS record object instead of being nested.

Output

JSON

  • id - Unique identifier of the DNS record.
  • name - Name of the DNS record.
  • type - Type of DNS record (e.g., A, CNAME, MX).
  • value - Value associated with the DNS record.
  • userDefinedFields - Array of user-defined fields related to the DNS record, unless flattened.
  • _label - Human-readable labels for picklist or reference fields if enabled.

Dependencies

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

Troubleshooting

  • Ensure the 'Advanced Filter' JSON string is correctly formatted and follows the Autotask API query syntax; invalid JSON or incorrect filter structure will cause errors.
  • If no records are returned, verify that the filter criteria match existing DNS records in Autotask.
  • When 'Get All' is false, ensure 'Max Records' is set within the allowed range (1-500) to avoid errors.
  • If picklist or reference labels are not appearing as expected, check that the corresponding options 'Add Picklist Labels' and 'Add Reference Labels' are enabled.
  • Network or authentication errors may occur if the Autotask API key credential is missing, invalid, or lacks necessary permissions.

Links

Discussion