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 interacts with the Domain Registrar resource of the Autotask REST API, specifically supporting the 'Get' operation to retrieve details about a specific domain registrar by its ID. It is useful for workflows that need to fetch domain registrar information for automation, reporting, or integration purposes, such as verifying domain registrar details or syncing domain data with other systems.
Properties
| Name | Meaning |
|---|---|
| Domain Registrar ID | The unique identifier of the domain registrar to retrieve information for. This is a required input to specify which domain registrar record to fetch. |
| Add Picklist Labels | Determines whether to automatically add '_label' fields for picklist fields in the response, providing human-readable values alongside raw data. No labels are added for empty values. |
| Add Reference Labels | Determines whether to automatically add '_label' fields for reference fields in the response, providing human-readable values alongside raw data. No labels are added for empty values. |
| 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 regardless of selection. |
| Flatten User-Defined Fields | When enabled, user-defined fields (UDFs) are brought up to the top level of each object in the response instead of being nested inside a userDefinedFields array, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the domain registrar.name- The name of the domain registrar.otherFields- Additional fields returned by the API for the domain registrar, including any selected columns and user-defined fields, possibly with added '_label' fields for picklist and reference types.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Domain Registrar ID is missing or invalid, the node will throw an error indicating the ID is required or not found. Ensure the ID is correct and exists in the Autotask system.
- If API authentication fails, verify that the Autotask API credentials are correctly configured and have sufficient permissions.
- Selecting invalid or non-existent columns in 'Select Columns' may result in incomplete or error responses. Use the provided dropdown or valid field IDs.
- Enabling 'Flatten User-Defined Fields' may cause naming conflicts if UDF names overlap with standard fields; use with caution.