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 using an advanced filtering mechanism. It allows users to specify complex query criteria in JSON format to filter the contact group contacts returned. This is useful for scenarios where you need to extract a customized list of contacts belonging to contact groups based on specific conditions, such as filtering by group attributes, contact details, or other metadata. For example, a user might want to get all contacts in certain groups that meet particular criteria for targeted communications or reporting.
Properties
| Name | Meaning |
|---|---|
| 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. |
| Advanced Filter | A required JSON string containing a 'filter' array that defines the Autotask API query criteria to filter contact group contacts. This allows for complex and precise filtering based on Autotask's query syntax. |
| Add Picklist Labels | If enabled, adds additional fields with '_label' suffix for picklist fields to provide human-readable values alongside the raw data. |
| Add Reference Labels | If enabled, adds additional fields with '_label' suffix for reference fields to provide human-readable 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. |
| Flatten User-Defined Fields | If enabled, user-defined fields (UDFs) are moved 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.picklistField_label- Human-readable label for picklist fields, if 'Add Picklist Labels' is enabled.referenceField_label- Human-readable label for reference fields, if 'Add Reference Labels' is enabled.otherFields- Other standard and custom fields returned based on the selected columns and filter criteria.
Dependencies
- Requires an Autotask API key credential for authentication to access the Autotask REST API.
Troubleshooting
- Invalid JSON in 'Advanced Filter' property can cause query failures. Ensure the JSON string is well-formed and follows Autotask API query syntax.
- Requesting too many records without 'Get All' enabled may result in incomplete data. Use 'Get All' to retrieve all matching records or increase 'Max Records' within allowed limits.
- Selecting fields that do not exist or are misspelled in 'Select Columns' may cause errors or missing data in the response.
- If labels for picklist or reference fields are not appearing, verify that 'Add Picklist Labels' and 'Add Reference Labels' are enabled and that the fields have non-empty values.
- API authentication errors may occur if the Autotask API key credential is missing, invalid, or expired. Verify credentials in node settings.
Links
- Autotask API Basic Query Calls - Official Autotask documentation describing how to construct query filters for API calls.