Actions64
- Instancia Actions
- Mensagem Actions
- Grupo Actions
- Chat Actions
- Perfil Actions
- Evento Actions
- Integração Actions
Overview
The "Evolution API Direct" node allows users to interact directly with the Evolution API by specifying a resource and operation, along with necessary parameters such as server URL and API key. It is designed for flexible integration scenarios where direct API calls are needed without predefined wrappers.
Specifically, for the Integração resource and Dify operation, this node facilitates managing Dify bots through various actions like creating, updating, deleting, checking status, fetching sessions, and changing session statuses. This is useful in automating chatbot management workflows, integrating bot lifecycle controls into broader automation pipelines, or synchronizing bot states with other systems.
Practical examples include:
- Automatically creating or updating a Dify bot configuration based on external triggers.
- Fetching active sessions of a Dify bot to monitor user interactions.
- Changing the status of a bot session (e.g., pausing or closing) programmatically.
Properties
| Name | Meaning |
|---|---|
| Server URL | The full URL of your Evolution API server endpoint. Example: https://api.exemplo.com. |
| API Key | The API key credential required to authenticate requests to the Evolution API instance. |
| Nome Da Instancia | The name of the instance that will send the message (used only for certain operations). |
| O Que Deseja Fazer | The action to perform on the Dify integration. Options: Add Dify, Check Dify, Update Dify, Delete Dify, Search Session in Dify, Change Session Status in Dify. |
| ID Do Dify | The identifier of the specific Dify bot to target. Leave empty to fetch all (used in find, update, delete, fetch sessions, change status operations). |
| Url Do Dify | The URL of your Dify bot (required for create and update operations). |
| ApiKey Do Dify | The API key for your Dify bot (required for create and update operations). |
| Tipo De Gatilho | Trigger type for the Dify bot. Options: Keyword, All (required for create and update). |
| Operador Do Gatilho | Operator for the trigger keyword matching. Options: Contains, Equals, Starts With, Ends With, Regex (only when trigger type is Keyword). |
| Gatilho | The word, phrase, or regex pattern used as a trigger to start the Dify bot (required when trigger type is Keyword). |
| Expira Em (Minutos) | Number of minutes without responses after which the bot should be deactivated (required for create and update). |
| Palavra Chave De Finalização | The keyword or phrase used to close/end the bot session (required for create and update). |
| Delay Padrão Da Mensagem (Em Milésimos) | Default delay in milliseconds before sending messages (required for create and update). |
| Palavra Chave De Finalização (unknownMessage) | Message shown when input is not recognized (required for create and update). |
| Escuta Mensagens Enviadas Por Mim | Boolean flag indicating whether the bot listens to messages sent by the user themselves (create and update). |
| Pausa O Bot Quando Eu Enviar Uma Mensagem | Boolean flag to pause the bot when the user sends a message (create and update). |
| Mantem a Sessão Do Bot Aberta | Boolean flag to keep the bot session open (create and update). |
| Tempo De Espera (Em Segundos) | Time in seconds the bot waits for additional messages before combining them into one (create and update). |
| Numero Do Destinatario | The remoteJid (recipient identifier) for changing session status (required for changeStatusDify operation). |
| Status | The new status of the session. Options: Opened, Paused, Closed (used in changeStatusDify operation). |
Output
The node outputs JSON data representing the response from the Evolution API corresponding to the requested Dify operation. The structure varies depending on the operation:
- For creation or update operations, it typically returns confirmation details about the bot configuration.
- For retrieval operations (findDify, fetchSessionsDify), it returns lists or objects describing bots or sessions.
- For deletion or status change operations, it returns success/failure confirmation.
No binary data output is indicated.
Dependencies
- Requires access to the Evolution API endpoint specified by the user.
- Requires valid API keys both for the Evolution API instance and for the Dify bot when applicable.
- No additional external dependencies beyond standard HTTP request capabilities.
- Proper network connectivity and permissions to call the specified URLs.
Troubleshooting
Common issues:
- Invalid or missing API keys leading to authentication errors.
- Incorrect or malformed URLs causing connection failures.
- Missing required parameters for specific operations.
- Using an unsupported operation or resource combination.
Error messages:
"Operação não suportada."indicates the selected operation is not implemented or recognized; verify the operation name.- Network or HTTP errors may occur if the server URL is unreachable or credentials are invalid.
Resolutions:
- Double-check API keys and URLs.
- Ensure all required fields for the chosen operation are filled.
- Confirm the operation and resource names match supported values.
Links and References
- Evolution API Documentation (as referenced in the node's base URL)
- Dify bot official documentation (not provided here, but recommended to consult for bot-specific parameters and usage)