Evolution APIInstall

Overview

This node integrates with the Evolution API v2 to perform various operations related to WhatsApp messaging and instance management. Specifically, for the Chat resource and the Buscar Contatos (Find Contacts) operation, it allows users to search for contacts within a specified WhatsApp instance.

Common scenarios where this node is beneficial include:

• Automating contact lookups in WhatsApp instances.
• Integrating WhatsApp contact data retrieval into workflows for customer support or marketing automation.
• Enriching datasets by fetching contact details dynamically during workflow execution.

For example, a user can input an instance name and a phone number to verify if that contact exists or retrieve contact information from the WhatsApp instance managed by Evolution API.

Properties

(Note: The provided properties JSON only includes "Instance Name" as input for this resource-operation.)

Output

The output is a JSON array containing the results returned by the Evolution API for the contact search. The structure typically includes:

• Contact details or confirmation of contact existence.
• A success boolean indicating if the operation was successful.
• A timestamp marking when the response was generated.

If the API returns multiple items, they are parsed into an array of objects. If the response is a string, the node attempts to parse it as JSON; otherwise, it wraps it in a generic object.

No binary data output is indicated for this operation.

Dependencies

• Requires an API key credential for authenticating requests to the Evolution API v2.
• The node uses HTTP requests to the Evolution API endpoints.
• Proper configuration of the API authentication credential in n8n is necessary.
• The user must specify the correct instance name corresponding to their WhatsApp instance managed via Evolution API.

Troubleshooting

• Common Issues:

  • Incorrect or missing instance name may cause the API call to fail or return no results.
  • Invalid or expired API credentials will result in authentication errors.
  • Network connectivity issues can prevent communication with the Evolution API.

• Error Messages:

  • Authentication failures usually indicate invalid API keys or misconfigured credentials.
  • "Operation failed" or similar messages may occur if the instance does not exist or is not connected.
  • JSON parsing errors might happen if the API returns unexpected string responses; these are caught and handled gracefully by the node.

• Resolutions:

  • Verify the instance name matches exactly the one registered in Evolution API.
  • Ensure API credentials are correctly set up and have sufficient permissions.
  • Check network access and endpoint availability.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.

Links and References

• Evolution API Documentation (hypothetical link)
• n8n HTTP Request Node Documentation
• WhatsApp Business API Overview

Note: The above summary is based solely on static analysis of the provided source code and property definitions without runtime execution.