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 contact group contacts from the Autotask system. It is useful for scenarios where you need to fetch a list of contacts associated with contact groups, such as for reporting, synchronization, or bulk processing. For example, you can use it to get all contacts in a specific contact group or to retrieve a limited number of contacts with selected fields for integration with other systems.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines which fields of the contact group contacts to retrieve and map in the output. Supports custom mapping and selection of specific fields. |
| Get All | Determines whether to return all matching contact group contacts or limit the results to a specified maximum number. |
| Max Records | Specifies the maximum number of contact group contacts to return when 'Get All' is false. The value must be between 1 and 500. |
| Add Picklist Labels | If enabled, adds additional fields with human-readable labels for picklist fields in the output, improving readability. |
| Add Reference Labels | If enabled, adds additional fields with human-readable labels for reference fields in the output. |
| 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. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are brought to the top level of each returned object instead of being nested inside a userDefinedFields array. |
Output
JSON
id- Unique identifier of the contact group contact.contactGroupId- Identifier of the contact group to which the contact belongs.contactId- Identifier of the contact.userDefinedFields- Array of user-defined fields associated with the contact group contact, unless flattened.
_label - Human-readable label for picklist or reference fields, if enabled.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- If no records are returned, verify that the contact group exists and contains contacts.
- Ensure the API credentials are valid and have sufficient permissions to read contact group contacts.
- If the node returns an error about unsupported resource or operation, confirm that 'Contact Group Contacts' resource and 'Get Many' operation are selected.
- When selecting fields, ensure that field names or IDs are valid; invalid fields may cause errors or empty results.
- If the maximum records limit is set too low, you may not get all desired data; consider enabling 'Get All' to retrieve all records.
Links
- Autotask Contact Group Contacts API Documentation - Official Autotask documentation describing the Contact Group Contacts resource and its fields.
- n8n Autotask Node Documentation - General documentation for the Autotask node in n8n, including usage and configuration.