Autotask icon

Autotask

Consume Autotask REST API
Join our community

Actions389

Overview

This node interacts with the Autotask REST API to retrieve a specific DNS record configuration item by its ID. It is useful for IT service management workflows where you need to fetch detailed DNS record information from Autotask for monitoring, auditing, or integration with other systems. For example, you can use this node to get DNS record details to verify configurations or to trigger further automation based on DNS record data.

Properties

Name Meaning
DNS Record ID The unique identifier of the DNS record to retrieve.
Add Picklist Labels Determines whether to add human-readable '_label' fields for picklist fields in the response, enhancing readability.
Add Reference Labels Determines whether to add human-readable '_label' fields for reference fields in the response.
Select Columns Names or IDs. Specifies which fields to include in the response. If none are selected, all fields are returned. The ID field is always included.
Flatten User-Defined Fields If enabled, user-defined fields (UDFs) are moved to the top level of the output object instead of being nested inside an array.

Output

JSON

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

Dependencies

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

Troubleshooting

  • If the DNS Record ID is invalid or not found, the node will throw an error indicating the record does not exist. Verify the ID is correct.
  • If authentication fails, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
  • Selecting specific columns that do not exist may result in incomplete data or errors; verify field names or IDs are valid.
  • Enabling flattening of user-defined fields may cause naming conflicts if UDF names overlap with standard fields.

Discussion