Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

This node, named "Evolution API," is designed to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Procurar Chats" (Find Chats), it allows users to search for chat messages within a specified instance and contact. This can be useful in scenarios where you want to retrieve chat history or specific messages from a messaging platform integrated via the Evolution API.

Practical examples include:

  • Fetching recent chat messages from a particular contact.
  • Paginating through chat history by specifying page number and number of chats per page.
  • Retrieving a specific message by its ID within a chat.

Properties

Name Meaning
Nome Da Instância The name of the instance where the chat is located.
Contato The contact's phone number or identifier whose chats are being searched.
ID Da Mensagem The unique identifier of the message to find within the chat.
Página The page number for paginated results (which page of chats to retrieve).
Quantidade Por Página The number of chat entries to return per page (page size).

Output

The node outputs an array of JSON objects representing the chat data retrieved from the Evolution API based on the input parameters. Each object corresponds to a chat message or chat metadata matching the search criteria.

If the node supports binary data output (not explicitly shown in the provided code), it would typically represent media attachments or files related to the chats, but this is not evident from the static analysis.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API service.
  • The node depends on the Evolution API endpoint that supports chat searching operations.
  • No additional environment variables or external services are explicitly required beyond the configured API credentials.

Troubleshooting

  • Unsupported Operation Error: If the operation or resource is not supported, the node throws an error stating the operation is not supported. Ensure that the Resource is set to "chat-api" and Operation to "find-chats" as expected.
  • Missing Required Parameters: Since properties like instance name, contact, and message ID are required, missing these will likely cause errors or empty results. Verify all required fields are filled correctly.
  • API Authentication Issues: If the API key or credentials are invalid or expired, the node will fail to authenticate. Check the configured credentials.
  • Pagination Limits: Setting very high values for page or offset might lead to performance issues or API rate limits. Use reasonable pagination settings.

Links and References

Discussion