Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The node "Evolution API Direct" allows users to interact directly with the Evolution API by specifying a server URL and an API key. Specifically, for the Chat resource and the Bloquear Contato (Block Contact) operation, it enables blocking or unblocking a contact by their phone number. This is useful in scenarios where you want to programmatically manage chat contacts' access, such as preventing unwanted messages or restoring communication.
Practical examples include:
- Automatically blocking spam or suspicious contacts.
- Unblocking a previously blocked contact after verification.
- Integrating contact management into automated workflows for customer support or marketing.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API server endpoint (e.g., https://api.exemplo.com). |
| API Key | The API key credential required to authenticate requests to the Evolution API instance. |
| Nome Da Instância | The name of the specific Evolution API instance you are targeting. |
| Contato | The phone number of the contact to block or unblock. |
| Ação | The action to perform: either "Bloquear" (block) or "Desbloquear" (unblock) the contact. |
Output
The node outputs a JSON array containing the response from the Evolution API after attempting to block or unblock the specified contact. The exact structure depends on the API's response but typically includes confirmation of the action's success or failure and any relevant metadata.
No binary data output is indicated.
Dependencies
- Requires access to an Evolution API server reachable via the provided Server URL.
- Requires a valid API key credential for authentication.
- The node expects the user to provide the instance name corresponding to the Evolution API environment.
- No additional external dependencies beyond standard HTTP request capabilities.
Troubleshooting
Common Issues:
- Incorrect Server URL or unreachable API endpoint will cause connection failures.
- Invalid or missing API key will result in authentication errors.
- Providing an incorrect contact number format may lead to API rejection.
- Using unsupported operations or resources will throw an error indicating the operation is not supported.
Error Messages:
"Operação não suportada."means the selected operation is not implemented for the chosen resource; verify that "Chat" and "Bloquear Contato" are correctly selected.- Authentication errors usually indicate invalid API keys; ensure the key is correct and has necessary permissions.
- Network errors suggest connectivity issues with the Evolution API server.
Links and References
- Evolution API official documentation (replace with actual URL): https://doc.evolution-api.com/api-reference
- n8n documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/