Evolution API icon

Evolution API

Complete WhatsApp automation with Evolution API
Join our community

Actions48

Overview

The "Get Group Info" operation of the Evolution API node allows users to retrieve detailed information about a specific WhatsApp group by providing its group ID. This is useful for scenarios where you need to programmatically access metadata or status about a WhatsApp group, such as its subject, participants, creation date, or other group-related details.

Practical examples include:

  • Monitoring group settings or membership changes.
  • Integrating group info into dashboards or CRM systems.
  • Automating workflows that depend on group attributes.

Properties

Name Meaning
Group ID The unique identifier of the WhatsApp group whose information you want to retrieve.
Additional Fields Optional extra parameters (Delay, Link Preview, Quoted Message ID, Mentions) - not used in this operation but available for message-related operations.

Output

The output JSON contains the response from the Evolution API endpoint /group/findGroup/{instanceName} with the provided group ID. It typically includes detailed information about the WhatsApp group such as:

  • Group subject/name
  • Group ID/JID
  • List of participants and their roles
  • Creation timestamp
  • Other metadata related to the group

The exact structure depends on the API response but generally provides comprehensive group details.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for the Evolution API service.
  • Requires an instance name configured in the credentials to target the correct WhatsApp instance.
  • Optionally uses another API key credential for a validation step via the n8n Tools API before making the main request.
  • The node makes HTTP POST requests to the Evolution API base URL combined with the instance name and operation-specific path.

Troubleshooting

  • Invalid Credentials: If the API key or instance name is incorrect, the node will fail authentication. Verify your API keys and instance configuration.
  • Group Not Found: Providing an invalid or non-existent group ID will result in an error or empty response. Double-check the group ID format.
  • API Validation Failure: The node performs a validation call to the n8n Tools API before the main request. Errors like 401 or 403 indicate invalid subscription or API key for this validation service.
  • Network Issues: Ensure the Evolution API base URL is reachable from your n8n environment.
  • Unexpected Errors: The node throws errors if unknown operations or resources are specified; ensure the operation is set exactly to "Get Group Info" under the "Group" resource.

Links and References

Discussion