Actions389
- Contract Actions
- Ticket History Actions
- Ticket Note Webhook Actions
- Ticket Note Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Role Actions
- Resource Role Actions
- Search Filter Actions
- Service Actions
- Skill Actions
- Service Call Actions
- Survey Results Actions
- Survey Actions
- Ticket Actions
- Opportunity Actions
- Notification History Actions
- Invoice Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Phase Actions
- Project Task Actions
- Project Note Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Service Bundle Adjustment Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Rate Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Role Costs Actions
- Contact Groups Actions
- Contact Actions
- Contact Webhook Actions
- Contact Group Contacts Actions
- Contract Block Hour Factor Actions
- Contract Block Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Company Alert Actions
- Company Actions
- Billing Code Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Overview
This node operation retrieves multiple Configuration Item DNS Record entries from the Autotask system. It is useful for scenarios where you need to fetch a list of DNS records associated with configuration items, such as for inventory management, auditing, or integration with other systems. For example, you can use it to get all DNS records related to configuration items in your IT environment, optionally limiting the number of records or retrieving all available records.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the Configuration Item DNS Record resource to map and include in the output. Allows precise control over the data returned. |
| Get All | Boolean flag to determine whether to return all matching DNS record entries or limit the results. |
| Max Records | Specifies the maximum number of DNS record entries to return when 'Get All' is false. The value must be between 1 and 500. |
| Add Picklist Labels | Determines whether to add human-readable label fields for picklist fields in the output. This helps interpret picklist values more easily. |
| Add Reference Labels | Determines whether to add human-readable label fields for reference fields in the output, improving readability of referenced data. |
| Select Columns Names or IDs. | Allows selection of specific fields (columns) 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 DNS record.name- Name of the DNS record.type- Type of the 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- Additional label fields for picklist or reference fields if enabled, providing human-readable values.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the resource and operation parameters are correctly set to 'configurationItemDnsRecord' and 'getMany'.
- Ensure the API credentials are valid and have sufficient permissions to read DNS records.
- If the node returns an error about unsupported resource, confirm that the resource name is exactly 'configurationItemDnsRecord'.
- When selecting fields, if no fields appear, try refreshing the node or checking the resource mapping configuration.
- If the maximum records limit is set too low, you might not get all expected data; consider enabling 'Get All' to retrieve all records.