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
The Domain Registrar 'Get Many' operation in this node retrieves multiple domain registrar records from the Autotask REST API. It is useful for scenarios where users need to fetch a list of domain registrars, for example, to display them in a dashboard, synchronize with other systems, or perform bulk processing. Users can control the number of records returned and select specific fields to include in the output, enabling efficient data handling and customization.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the domain registrar records to retrieve and map in the output. Supports custom mapping and auto-mapping of fields. |
| Get All | Boolean flag to determine whether to return all available domain registrar records or limit the results. |
| Max Records | Specifies the maximum number of domain registrar records 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, enhancing readability. |
| Add Reference Labels | Determines whether to add human-readable '_label' fields for reference fields in the output. |
| 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 brought to the top level of each record object instead of being nested, simplifying access. |
Output
JSON
id- Unique identifier of the domain registrar record.fields- Values of the selected fields for each domain registrar record, where corresponds to the field IDs or names mapped._label - Human-readable labels for picklist or reference fields if 'Add Picklist Labels' or 'Add Reference Labels' options are enabled.userDefinedFields- User-defined fields nested inside the userDefinedFields array, unless 'Flatten User-Defined Fields' is enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If no records are returned, verify that the domain registrar resource exists and that the API credentials have sufficient permissions.
- If the node returns an error about unsupported resource, ensure the resource parameter is set to 'DomainRegistrar'.
- When selecting fields, ensure the field IDs or names are valid; invalid fields may cause errors or empty data.
- If the maximum records limit is exceeded, reduce the 'Max Records' value or enable 'Get All' to fetch all records.
- Network or authentication errors may occur if the API key is invalid or network connectivity is lost; verify credentials and network status.