Wappfy icon

Wappfy

Interact with WhatsApp through Wappfy API

Overview

This node allows you to interact with WhatsApp groups via the Wappfy API, specifically enabling you to update the subject (name) of a WhatsApp group. This operation is useful when you want to programmatically rename a group based on changing contexts or automate group management workflows.

Practical examples include:

  • Automatically renaming a project group when the project name changes.
  • Updating event group names dynamically as event details evolve.
  • Standardizing group names across multiple WhatsApp groups in an organization.

Properties

Name Meaning
Group ID The unique identifier of the WhatsApp group to update.
Subject The new subject (name) for the group.

Output

The output JSON contains the response from the Wappfy API after attempting to update the group subject. Typically, this will include confirmation of the update or details about the updated group. The exact structure depends on the API response but generally includes fields indicating success or failure and the updated group data.

No binary data output is involved in this operation.

Dependencies

  • Requires an active Wappfy API credential configured in n8n, including:
    • Base URL of the Wappfy API.
    • Instance name identifying the WhatsApp session.
    • An API key for authentication.
  • The node sends HTTP PUT requests to the Wappfy API endpoint /api/{instanceName}/groups/{groupId}/subject with the new subject in the request body.

Troubleshooting

  • Common issues:

    • Invalid or missing Group ID: Ensure the Group ID corresponds to an existing WhatsApp group.
    • Insufficient permissions: The API key must have rights to modify group information.
    • Network or API endpoint errors: Verify the base URL and instance name are correct and the Wappfy service is reachable.
  • Error messages:

    • "404 Not Found": The specified group does not exist or the Group ID is incorrect.
    • "401 Unauthorized" or "403 Forbidden": Authentication failed or the API key lacks necessary permissions.
    • "400 Bad Request": The new subject may be invalid or missing; ensure it is a non-empty string.

To resolve errors, verify all input parameters, credentials, and network connectivity.

Links and References

Discussion