API endpoint: Calls GET /{groupId}?fields=id,subject,description. Returns the group subject, description, and ID. Use group/getParticipants to retrieve the member list separately.
When to Use
- Group existence verification: Before sending a message to a group, a workflow calls this node to confirm the group still exists and has not been deleted since it was created.
- Subject change detection: A reconciliation workflow retrieves the current group subject and compares it against the database record to detect and log any external renames.
- Description audit: A compliance workflow retrieves group descriptions to verify they still comply with content policies before continuing to use the group for business communications.
- Dashboard enrichment: A portal workflow retrieves live group details to display current group names and descriptions in an admin dashboard rather than relying on stale cached data.
- Pre-update verification: Before calling
group/update, retrieve current values to confirm a change is actually needed and log the before-state for audit purposes.
Configuration
Connection
| Field | Required | Description |
accessToken | Required | Permanent System User access token. Store in BizFirst Credentials Manager. |
phoneNumberId | Required | Numeric string ID of the business phone number that is a member/admin of the group. |
apiVersion | Optional | Meta Graph API version. Defaults to v18.0. |
Operation
| Field | Required | Description |
groupId | Required | The WhatsApp group ID (e.g. 120363xxxxxxxxxx@g.us) stored when the group was created. |
Sample Configuration
{
"resource": "group",
"operation": "get",
"accessToken": "{{ $credentials.whatsAppToken }}",
"phoneNumberId": "123456789012345",
"groupId": "120363xxxxxxxxxx@g.us"
}
Validation Errors
| Error | Cause |
accessToken is required | The accessToken field is empty. |
phoneNumberId is required | No Phone Number ID supplied. |
groupId is required | No group ID provided. |
100 (Meta) | Group not found — the group has been deleted or the phone number is not a member. |
200 (Meta) | Insufficient permissions to read this group. |
Output
Success Port
| Field | Type | Description |
groupId | string | The group ID. |
subject | string | Current group name/subject. |
description | string | Current group description. May be null if not set. |
status | string | "success". |
rawResponse | string | Full raw JSON from the Meta Graph API. |
Error Port
| Field | Type | Description |
groupId | string | Group ID echoed from input. |
status | string | "failed" or "error". |
errorCode | string | Meta error code or "timeout". |
errorMessage | string | Human-readable error description. |
Sample Output
{
"groupId": "120363xxxxxxxxxx@g.us",
"subject": "Project Alpha Team",
"description": "Daily standup and project updates for Project Alpha.",
"status": "success"
}
Expression Reference
| Value | Expression | Notes |
| Group subject | {{ $output.getGroup.subject }} | Compare to expected name to detect external renames. |
| Group description | {{ $output.getGroup.description }} | Display in admin portals or audit reports. |
| Group ID | {{ $output.getGroup.groupId }} | Confirm the correct group was retrieved before performing operations on it. |
Node Policies & GuardRails
| Policy Area | Recommendation |
| Credential storage | Store the access token in BizFirst Credentials Manager. |
| Error port | Connect the error port. A 100 not-found error means the group was deleted externally — update your database accordingly and halt downstream group operations. |
| Stale data prevention | Do not cache group metadata for more than a few minutes. Group subjects and descriptions can change at any time by any group admin. |
Examples
Group Existence Check Before Broadcast
{
"resource": "group",
"operation": "get",
"accessToken": "{{ $credentials.whatsAppToken }}",
"phoneNumberId": "123456789012345",
"groupId": "{{ $input.groupId }}"
}
Before a scheduled group broadcast, this node confirms the group still exists. If a 100 error is returned, the workflow branches to an error path that marks the group as deleted in the database and notifies the operator to create a new group before retrying the broadcast.
Pre-Rename Audit
{
"resource": "group",
"operation": "get",
"accessToken": "{{ $credentials.whatsAppToken }}",
"phoneNumberId": "123456789012345",
"groupId": "{{ $workflow.groupId }}"
}
Before a group rename operation, this node captures the current subject and logs it as the "before" state. After group/update succeeds, the "before" and "after" values are written to the audit log with the timestamp and the identity of the workflow that initiated the rename.