Actions64
- Instancia Actions
- Mensaje Actions
- Grupo Actions
- Crear Grupo
- Actualizar Imagen Del Grupo
- Actualizar Nombre Del Grupo
- Actualizar Descripción Del Grupo
- Actualizar Configuraciones
- Actualizar Miembros
- Buscar Enlace De Invitación
- Revocar Enlace De Invitación
- Enviar Enlace De Invitación
- Buscar Grupos
- Encontrar Participantes
- Mensajes Temporales
- Unirse Al Grupo
- Salir Del Grupo
- Chat Actions
- Perfil Actions
- Evento Actions
- Integración Actions
Overview
The node interacts with the "Evolution API" to perform various operations related to chat management. Specifically, for the "Chat" resource and the "Bloquear Contacto" (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 automated control over chat contacts is needed, such as managing spam, restricting communication, or unblocking previously blocked contacts.
Practical examples:
- Automatically blocking a phone number that sends unwanted messages.
- Unblocking a contact after resolving an issue.
Properties
Name | Meaning |
---|---|
Nombre De La Instancia | The name of the instance to connect to the Evolution API. |
Contacto | The phone number of the contact to block or unblock. |
Acción | The action to execute on the contact: either "Bloquear" (block) or "Desbloquear" (unblock). |
Output
The node outputs a JSON array containing the result of the block or unblock operation. The exact structure depends on the 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 base URL for requests is
https://doc.evolution-api.com/api-reference
. - Proper configuration of the node with the instance name and valid contact number is necessary.
Troubleshooting
Common issues:
- Invalid or missing instance name may cause connection failures.
- Incorrect contact number format might lead to errors from the API.
- Attempting unsupported operations will throw an error indicating the operation is not supported.
Error messages:
"Operação não suportada."
means the requested operation is not supported for the selected resource.- API authentication errors if the API key is invalid or missing.
Resolutions:
- Verify the instance name and ensure it matches the configured Evolution API instance.
- Confirm the contact number is correctly formatted.
- Check that the API key credential is properly set up and has required permissions.
Links and References
- Evolution API Documentation (official API reference)