Evolution API icon

Evolution API

Interact with Evolution API

Overview

The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Listar Contatos" (List Contacts), it enables users to retrieve contact information from an instance of the Evolution API chat system. This can be useful in scenarios where you want to automate fetching contact lists or details about specific contacts within a chat application integrated via Evolution API.

Practical examples include:

  • Automatically syncing contacts from the Evolution API chat into another CRM or database.
  • Fetching a specific contact's details by their number for further processing or messaging.
  • Listing all contacts to generate reports or trigger workflows based on contact data.

Properties

Name Meaning
Nome Da Instância The name of the Evolution API instance to connect to.
Listar Todos Boolean option to list all contacts (true) or not (false).
Contato Specific contact number to fetch when Listar Todos is set to false.

Output

The node outputs a JSON array containing the contact(s) retrieved from the Evolution API. Each item in the array represents a contact object with its associated details as returned by the API. The exact structure depends on the Evolution API response but typically includes identifiers like contact number, name, and other metadata.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.
  • The node expects the Evolution API base URL and headers to be configured internally.
  • No additional external dependencies are specified beyond the Evolution API service.

Troubleshooting

  • Unsupported Operation Error: If the operation selected is not supported, the node throws an error stating the operation is not supported for the resource. Ensure that the Resource is set to "chat-api" and Operation to "find-contacts" (Listar Contatos).
  • Missing Required Parameters: The node requires the instance name and either the flag to list all contacts or a specific contact number. Missing these will likely cause errors or empty results.
  • API Authentication Issues: Make sure the API key credential is correctly configured and valid; otherwise, authentication errors will occur.
  • Empty Results: If no contacts are found, verify that the instance name is correct and that the contact number exists if querying a specific contact.

Links and References

Discussion