Evolution API

Overview

The node interacts with the Evolution API to perform chat-related operations. Specifically, for the "Chat" resource and the "Block Contact" operation, it allows users to block or unblock a contact by specifying the contact's number. This is useful in scenarios where you want to programmatically manage your contact list's access, such as preventing unwanted messages or restoring communication with previously blocked contacts.

Practical examples:

• Automatically blocking spam or unknown numbers detected through other workflows.
• Unblocking a contact after resolving an issue or upon user request.

Properties

Output

The node outputs a JSON array containing the result of the block or unblock operation. The exact structure depends on the Evolution API response but generally includes confirmation of the action taken on the specified contact.

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 indicated beyond the Evolution API service.

Troubleshooting

• Operation not supported error: If the node throws an error stating the operation is not supported, verify that the resource is set to "chat-api" and the operation to "block-contact".
• Missing required parameters: Ensure that "Name Da Instância", "Contato", and "Ação" fields are correctly filled; missing these will cause execution failure.
• API authentication errors: Confirm that the API key credential is valid and has the necessary permissions.
• Invalid contact number format: The contact number should be in the expected format accepted by the Evolution API; otherwise, the API may reject the request.

Links and References

• Evolution API Documentation (base URL referenced in the code)
• n8n documentation on creating custom nodes