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 "Evolution API" allows users to interact with the Evolution API by performing various operations on different resources. Specifically, for the resource Instancia and operation Conectar Instancia, the node enables connecting to a particular instance by its name. This is useful in scenarios where you need to programmatically establish or verify connections to instances managed via the Evolution API.
Practical examples include:
- Automating the connection setup to a specific instance before running further workflows.
- Validating that an instance exists and is accessible by its given name.
- Integrating instance connection steps into larger automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the instance you want to connect to. This is a required string input field. |
Output
The node outputs a JSON array containing the result of the connection attempt to the specified instance. The exact structure depends on the Evolution API response but generally includes details about the connected instance or status information confirming the connection.
If the node supports binary data output, it is not indicated in the provided code or properties.
Dependencies
- Requires an API key credential for authenticating with the Evolution API.
- The base URL for requests is set to
https://doc.evolution-api.com/api-reference. - Proper configuration of the API authentication credentials within n8n is necessary.
Troubleshooting
- Operation not supported error: If you select an unsupported operation or resource, the node throws an error indicating the operation is not supported. Ensure you use valid combinations of resource and operation.
- Connection failures: If the instance name is incorrect or the API credentials are invalid, the connection will fail. Verify the instance name and API key.
- API errors: Any errors returned from the Evolution API (e.g., rate limits, unauthorized access) will be surfaced as node errors. Check your API usage and permissions.
Links and References
- Evolution API Documentation (base URL used in the node)
- n8n documentation on creating custom nodes