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 node operation 'Get Many' for the 'Contact Groups' resource retrieves multiple contact group records from the Autotask system. It allows users to fetch a list of contact groups with options to limit the number of records returned or retrieve all available records. This operation is useful for scenarios such as synchronizing contact group data, generating reports, or integrating contact group information into workflows.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the contact groups to retrieve and map in the output, allowing customization of the data returned. |
| Get All | Determines whether to return all contact group records or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of contact group records to return when 'Get All' is false. The value ranges from 1 to 500. |
| Add Picklist Labels | Indicates whether to add human-readable label fields for picklist fields in the output, enhancing readability. |
| Add Reference Labels | Indicates whether to add human-readable label fields for reference fields in the output. |
| Select Columns Names or IDs. | Allows selection of specific fields to include in the response by choosing from a list or specifying IDs via expressions. 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 brought to the top level of each contact group object instead of being nested, simplifying access to these fields. |
Output
JSON
id- Unique identifier of the contact group.name- Name of the contact group.description- Description of the contact group.userDefinedFields- Array of user-defined fields associated with the contact group, unless flattened.
_label - Human-readable labels for picklist or reference fields, added if enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the node returns no data, verify that the API credentials are correct and have sufficient permissions to access contact groups.
- If the maximum records limit is set too low, not all desired records will be returned; consider enabling 'Get All' to retrieve all records.
- Errors related to field mapping may occur if selected fields do not exist or are misspelled; ensure correct field names or IDs are used.
- Network or API errors may occur if the Autotask service is unreachable; check network connectivity and API endpoint status.