Actions53
- Instância Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Evento Actions
- Integração Actions
Overview
This node integrates with the Evolution API v2 to perform various operations related to WhatsApp instances, messages, groups, chats, events, and integrations. Specifically for the Chat resource and the Procurar Chats (findChats) operation, it allows users to search for chats associated with a given WhatsApp instance.
Common scenarios where this node is beneficial include:
- Automating chat management workflows by searching for existing chats.
- Integrating chat data retrieval into broader automation processes.
- Building custom dashboards or reports based on chat information.
For example, you could use this node to find all chats in a specific WhatsApp instance before sending targeted messages or analyzing chat activity.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the WhatsApp instance where the chat search will be performed. This is required to identify which instance's chats to query. |
Output
The output is a JSON array containing the results of the chat search. Each item in the array represents a chat object returned by the Evolution API. The structure of each chat object depends on the API response but typically includes details such as chat identifiers, participants, last message info, and status.
Additionally, the output includes metadata fields:
success: Boolean indicating if the operation was successful.timestamp: ISO string timestamp of when the operation completed.count: Number of chat items returned (if applicable).
If the API returns no data, a success message with a timestamp is provided instead.
This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Evolution API v2.
- The node uses HTTP requests to the Evolution API endpoints; therefore, internet connectivity and proper API access permissions are necessary.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Incorrect or missing instance name: Ensure the "Instance Name" property is correctly set and corresponds to a valid WhatsApp instance configured in the Evolution API.
- Authentication failures: Verify that the API key credential is valid and has sufficient permissions.
- Network errors: Check internet connectivity and API endpoint availability.
Error messages:
- Errors thrown by the node typically contain the API error message. If the node fails, check the error details for clues such as invalid parameters or unauthorized access.
- If the node returns an empty result or unexpected data, confirm that the instance has active chats and that the API endpoint is functioning properly.
Links and References
- Evolution API Documentation (hypothetical link as the real URL is not provided)
- n8n documentation on Creating Custom Nodes
- General WhatsApp Business API references for understanding chat concepts
Note: The above summary is based solely on static analysis of the provided source code and input properties.