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 detailed information about a specific Contact Group from the Autotask system using its unique Contact Group ID. It is useful for scenarios where you need to fetch and utilize contact group data within your workflows, such as syncing contact groups with other systems, reporting, or automation tasks that depend on group membership or attributes.
Properties
| Name | Meaning |
|---|---|
| Contact Group ID | The unique identifier of the contact group to retrieve. This is required to specify which contact group the operation will fetch. |
| Add Picklist Labels | Determines whether to automatically add human-readable "_label" fields for picklist fields in the response. This helps in understanding picklist values without needing to decode their IDs. |
| Add Reference Labels | Determines whether to automatically add human-readable "_label" fields for reference fields in the response, making reference data easier to interpret. |
| 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 to the top level of the returned object instead of being nested inside a userDefinedFields array, simplifying access to these fields. |
Output
JSON
id- The unique identifier of the contact group.name- The name of the contact group.description- Description or notes about the contact group.picklistField_label- Human-readable labels for picklist fields, if Add Picklist Labels is enabled.referenceField_label- Human-readable labels for reference fields, if Add Reference Labels is enabled.userDefinedFields- Array of user-defined fields associated with the contact group, unless flattened.userDefinedFieldName- User-defined fields brought to top-level properties if Flatten User-Defined Fields is enabled.
Dependencies
- Requires an API key credential for Autotask REST API authentication.
Troubleshooting
- If the Contact Group ID is invalid or not found, the node will throw an error indicating the resource could not be retrieved. Verify the ID is correct.
- If API authentication fails, ensure the Autotask API credentials are correctly configured and have sufficient permissions.
- Selecting fields that do not exist may result in incomplete data or errors; verify field names or IDs when using Select Columns.
- Enabling Add Picklist Labels or Add Reference Labels without proper API support may result in missing label fields.