Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
This node interacts with the "Evolution API" to perform various operations related to chat management. Specifically, for the Chat resource and the Bloquear Contato (Block Contact) operation, it allows users to block or unblock a contact by specifying the contact's number and the desired action. This is useful in scenarios where you want to programmatically control communication permissions, such as preventing unwanted messages or restoring contact access.
Practical examples include:
- Automatically blocking contacts flagged as spam.
- Unblocking a previously blocked contact after verification.
- Managing contact permissions in bulk via workflows.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to connect to the Evolution API. |
| Contato | The phone number or identifier 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 result of the block/unblock operation. Each item in the array corresponds to the response from the Evolution API for the requested action on the specified contact. The exact structure depends on the API response but generally confirms success or failure of the operation.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The node expects the user to configure this credential within n8n.
- Network connectivity to the Evolution API endpoint is necessary.
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" and Operation to "Bloquear Contato".
- Invalid contact number: Ensure the contact number format matches what the Evolution API expects.
- Authentication errors: Confirm that the API key credential is correctly configured and has sufficient permissions.
- Network issues: Check internet connectivity and API endpoint availability.
Links and References
- Evolution API official documentation (not provided in source; consult your API provider)
- n8n documentation on creating and using credentials
- General best practices for managing contact blocking in messaging APIs