Actions69
- App Actions
- Chat Actions
- Device Actions
- Group Actions
- Add Participant
- Approve Participant Request
- Create Group
- Demote Participant
- Export Group Participants
- Get Group Info
- Get Group Info From Link
- Get Group Invite Link
- Get Group Participants
- Get Participant Requests
- Join Group With Link
- Leave Group
- Promote Participant
- Reject Participant Request
- Remove Participant
- Set Group Announce Mode
- Set Group Locked Status
- Set Group Name
- Set Group Photo
- Set Group Topic
- Message Actions
- Newsletter Actions
- Send Actions
- User Actions
Group → Get Group Info
AI-generatedOverview
This node interacts with the Go WhatsApp Web MultiDevice API to retrieve detailed information about a specific WhatsApp group. It is useful for scenarios where you need to fetch metadata or current status of a group, such as its name, participants, settings, or other group-related details. For example, it can be used in automation workflows to monitor group changes or to display group info in a dashboard.
Use Case Examples
- Retrieve information about a WhatsApp group by providing its Group ID to monitor group membership or settings changes.
- Use the node to fetch group details before performing further group management operations like adding or removing participants.
Properties
| Name | Meaning |
|---|---|
| Device ID | Optional device ID override. If set, it takes priority over the credential device ID. |
| Group ID | ID of the group to retrieve information for. |
Output
JSON
groupId- The unique identifier of the group.groupName- The name of the group.participants- List of participants in the group.groupSettings- Settings and configurations of the group such as locked status, announcement mode, etc.
Dependencies
- Requires an API key credential for Go WhatsApp Web MultiDevice API with host URL configuration.
Troubleshooting
- Common issues include providing an invalid or missing Group ID, which will result in errors from the API indicating the group could not be found.
- If the device ID override is set incorrectly, the node may fail to authenticate or connect to the correct device session.
- Errors related to API connectivity or authentication usually indicate misconfigured credentials or network issues.