Clientes Online - WhatsApp icon

Clientes Online - WhatsApp

Interação com a Plataforma de Relacionamento via WhatsApp - Clientes.Online
Join our community

Actions59

Overview

This node interacts with a WhatsApp-based customer relationship platform to list contacts belonging to a specific organizational group. It is useful when you want to retrieve and process contact information grouped by organizational units or teams within the platform.

Typical use cases include:

  • Fetching all contacts in a particular group for targeted messaging or analysis.
  • Integrating group-based contact lists into workflows for marketing, support, or operational automation.
  • Paginating through large contact groups to handle data in manageable chunks.

For example, you might use this node to get all contacts from the "Sales Team" group to send them a promotional message or to update their details in another system.

Properties

Name Meaning
ID Do Grupo The unique identifier of the organizational group whose contacts you want to list.
Página The page number of the contacts list to retrieve, starting at 1. Used for pagination.

Output

The node outputs an array of contact objects in the json field. Each object represents a contact belonging to the specified group. The exact structure of each contact object depends on the platform's API but typically includes contact identifiers, names, phone numbers, and possibly other metadata.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the external WhatsApp customer relationship platform.
  • The node depends on the platform's API endpoints to fetch group contacts.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Missing or invalid group ID: If the "ID Do Grupo" property is empty or incorrect, the node will fail to retrieve contacts. Ensure the group ID is valid and exists in the platform.
  • Pagination issues: Requesting a page number beyond the available pages may return empty results. Verify the total number of pages or handle empty responses gracefully.
  • Authentication errors: If the API key credential is missing, expired, or invalid, the node will not authenticate successfully. Check and update the API credentials in n8n.
  • API rate limits or connectivity problems: Network issues or API rate limiting can cause failures. Review error messages and retry after some time if needed.

Links and References

Discussion