WAHA API icon

WAHA API

Complete WhatsApp automation with WAHA API - Multi-engine support
Join our community

Actions55

Overview

The "Get Group" operation of the WAHA API node allows users to retrieve detailed information about a specific WhatsApp group. This includes metadata and current state data for the group identified by its chat ID. It is useful in scenarios where automation workflows need to access group details, such as group name, participants, or settings, for monitoring, reporting, or further processing.

For example, you might use this node operation to:

  • Fetch group info before sending targeted messages.
  • Verify group membership or status before performing administrative actions.
  • Integrate WhatsApp group data into CRM or analytics platforms.

Properties

Name Meaning
Session Name The name of the WhatsApp session to use (defaults to a configured default session).
Chat ID The unique identifier of the WhatsApp group (e.g., groupid@g.us) whose information is fetched.
Additional Fields A collection of optional fields; not specifically used in "Get Group" but available for other operations.

Output

The output JSON contains the response from the WAHA API with the group's information. This typically includes group metadata such as group name, description, participants list, and other relevant group details as provided by the WhatsApp API via WAHA.

The node does not output binary data for this operation.

Example output structure (simplified):

{
  "id": "groupid@g.us",
  "name": "Group Name",
  "description": "Group description text",
  "participants": [
    {
      "id": "participant1@c.us",
      "isAdmin": true,
      "isSuperAdmin": false
    },
    {
      "id": "participant2@c.us",
      "isAdmin": false,
      "isSuperAdmin": false
    }
  ],
  "creation": "timestamp",
  ...
}

Dependencies

  • Requires an active WAHA API credential with a valid base URL and API key.
  • Requires a valid WhatsApp session name configured in the node or credentials.
  • Optionally uses an additional API validation service requiring its own API key and URL.
  • The node makes HTTP requests to the WAHA API endpoints.

Troubleshooting

  • Invalid Credentials: If the WAHA API key or session name is incorrect, the node will fail. Ensure credentials are correctly set up.
  • Unauthorized Errors: The node validates subscription/API keys against an external service. Unauthorized errors indicate invalid or expired API keys.
  • Unknown Group ID: Providing an invalid or non-existent group chat ID will result in an error or empty response.
  • Network Issues: Connectivity problems to the WAHA API endpoint can cause request failures.
  • Operation Not Supported: Using an unsupported operation or resource combination will throw an error indicating unknown operation or resource.

To resolve these issues:

  • Double-check API keys and session names.
  • Verify the group chat ID format (groupid@g.us).
  • Confirm network connectivity to the API endpoint.
  • Review node configuration for correct resource and operation selection.

Links and References

Discussion