WhatsApp — group/update

API endpoint: Calls POST /{groupId} with the new subject value. Admin privilege on the group is required. The update takes effect immediately and is visible to all participants.

When to Use

Project phase rename: When a project moves from one phase to another, a workflow automatically renames the group to reflect the new phase (e.g. "Project Alpha — Design" to "Project Alpha — Build").
Incident to post-mortem handoff: After an incident is resolved, the response workflow renames the group from "INC-001 Bridge" to "INC-001 Post-Mortem" to signal the shift in purpose.
Seasonal group refresh: A recurring workflow updates the subject of persistent customer groups to reflect the current season or promotion period.
Cohort graduation: An e-learning platform renames a study group from "Cohort 12 — Active" to "Cohort 12 — Alumni" when participants complete the course.
Compliance-driven normalisation: A compliance audit identifies groups with non-standard names. An automated remediation workflow renames them to the approved format.

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. Must be a group admin.
`apiVersion`	Optional	Meta Graph API version. Defaults to `v18.0`.

Operation

Field	Required	Description
`groupId`	Required	The WhatsApp group ID to update.
`subject`	Required	New group name. Max 25 characters.

Sample Configuration

{
  "resource": "group",
  "operation": "update-name",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "groupId": "120363xxxxxxxxxx@g.us",
  "subject": "Project Alpha — Build Phase"
}

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.
`subject is required`	No new group name provided.
`subject too long`	New subject exceeds 25 characters.
`100` (Meta)	Group not found or phone number is not a member.
`200` (Meta)	Phone number is a group member but not an admin — admin privilege required.

Output

Success Port

Field	Type	Description
`success`	bool	`true` when the group was renamed.
`groupId`	string	The updated group ID.
`subject`	string	The new group subject as stored.
`status`	string	`"updated"`.
`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

{
  "success": true,
  "groupId": "120363xxxxxxxxxx@g.us",
  "subject": "Project Alpha — Build Phase",
  "status": "updated"
}

Expression Reference

Value	Expression	Notes
Update success	`{{ $output.updateGroup.success }}`	Gate downstream steps on this boolean.
New subject	`{{ $output.updateGroup.subject }}`	Store in the local group record to keep the database in sync.

Node Policies & GuardRails

Policy Area	Recommendation
Credential storage	Store the access token in BizFirst Credentials Manager.
Admin requirement	The business phone number must be a group admin. If a `200` permission error is returned, verify admin status via `group/getParticipants` before retrying.
Audit logging	Log the old and new subject names with the group ID and timestamp to the audit trail for compliance record-keeping.
Subject length	Validate subject length (max 25 characters) in a Function node before calling this node to prevent avoidable API errors.
Error port	Connect the error port.

Examples

Automated Phase Transition Rename

{
  "resource": "group",
  "operation": "update-name",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "groupId": "{{ $input.groupId }}",
  "subject": "{{ $input.newPhaseName }}"
}

A project management system webhook fires when a project moves to a new phase. The workflow retrieves the associated group ID from the project record, constructs the new name from the project name and phase name (truncated to 25 characters by a Function node), and calls this update node. The audit log records the rename with a timestamp.

Incident Closure Rename

{
  "resource": "group",
  "operation": "update-name",
  "accessToken": "{{ $credentials.whatsAppToken }}",
  "phoneNumberId": "123456789012345",
  "groupId": "{{ $workflow.incidentGroupId }}",
  "subject": "INC-{{ $input.incidentId }} Post-Mortem"
}

When an incident is marked as resolved in the ITSM system, this workflow renames the bridge group to the post-mortem name, signalling to participants that the urgent response phase is over and the group will now be used for retrospective discussion.