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" provides integration with the Evolution API service, allowing users to perform various operations on different resources. Specifically for the resource Integración and operation Dify, it enables managing Dify bot instances through actions such as creating, verifying, updating, deleting bots, fetching sessions, and changing session statuses.
This node is beneficial in scenarios where automated chatbot management is required within workflows, such as:
- Creating new Dify bot instances dynamically.
- Verifying existing bots or retrieving their details.
- Updating bot configurations like triggers, messages, and session behaviors.
- Deleting bots that are no longer needed.
- Managing active chat sessions by fetching or changing their states.
Practical examples include automating customer support bots setup, monitoring bot sessions for analytics, or programmatically pausing/resuming bot conversations based on external events.
Properties
| Name | Meaning |
|---|---|
| Nombre De La Instancia | The name of the Dify bot instance to integrate with. |
| Qué Desea Hacer | Action to perform with the Dify integration: Add, Verify, Update, Delete, Fetch Sessions, Change Status. |
| ID De Dify | The unique identifier of the Dify bot (used for find, update, delete, fetch sessions, change status). |
| URL De Dify | The base URL of your Dify instance (required for create and update operations). |
| APIKey De Dify | The API key for authenticating with your Dify bot (required for create and update operations). |
| Tipo De Disparador | Trigger type for the bot: Keyword or All messages (for create and update). |
| Operador Del Disparador | Operator for trigger matching: Contains, Equals, Starts With, Ends With, Regex (only if trigger type is Keyword). |
| Disparador | The keyword, phrase, or regex pattern used to trigger the bot (required if trigger type is Keyword). |
| Expira En (Minutos) | Minutes of inactivity after which the bot will be deactivated (create and update). |
| Palabra Clave De Finalización | Keyword or phrase used to close/end the bot session (create and update). |
| Retraso Predeterminado Del Mensaje (En Milisegundos) | Default delay in milliseconds before the bot sends a message (create and update). |
| Mensaje Desconocido | Message shown when the bot does not understand user input (create and update). |
| Escucha Mensajes Enviadas Por Mim | Whether the bot listens to messages sent by the user themselves (create and update). |
| Pausa O Bot Quando Eu Enviar Uma Mensagem | Whether the bot pauses when the user sends a message (create and update). |
| Mantem a Sessão Do Bot Aberta | Whether to keep the bot session open continuously (create and update). |
| Tempo De Espera (Em Segundos) | Time in seconds the bot waits to combine multiple incoming messages into one (create and update). |
| Número Del Destinatario | RemoteJid (recipient identifier) for changing session status (changeStatus operation). |
| Estado | Session state to set: Opened, Paused, or Closed (changeStatus operation). |
Output
The node outputs JSON data representing the result of the performed operation. This typically includes:
- Details of created or updated Dify bots.
- Lists or single objects of Dify bots when searching or verifying.
- Session information when fetching sessions.
- Confirmation or status updates when changing session states or deleting bots.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs valid API credentials (API key) for authenticating requests to the Dify bot endpoints.
- Proper configuration of the Dify instance URL and API key is mandatory for create and update operations.
- The node expects the user to provide correct identifiers (IDs, RemoteJid) for operations targeting specific bots or sessions.
Troubleshooting
Common Issues:
- Missing or incorrect API URL or API key will cause authentication failures.
- Providing invalid bot IDs or session identifiers may result in "not found" errors.
- Incorrect trigger configurations (e.g., missing trigger value when trigger type is keyword) can lead to validation errors.
- Network connectivity issues with the Evolution API endpoint.
Error Messages:
"Operação não suportada."indicates an unsupported operation-resource combination; verify selected resource and operation.- Authentication errors suggest checking API keys and permissions.
- Validation errors often relate to missing required parameters; ensure all required fields are filled.
Resolutions:
- Double-check all required inputs, especially URLs, API keys, and IDs.
- Confirm that the chosen operation matches the intended action.
- Ensure network access to the Evolution API service.
- Review the trigger settings carefully when creating or updating bots.
Links and References
- Evolution API Documentation (official API reference)
- Dify bot platform documentation (refer to your Dify provider for detailed API usage)
- n8n documentation on custom nodes and API integrations for further customization guidance