Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key

Actions64

Overview

The node "Evolution API Direct" allows users to interact directly with the Evolution API by specifying a server URL and an API key. Specifically, for the Resource "Grupo" and Operation "Sair Do Grupo" (Leave Group), this node enables a user or system to leave a specified group by providing the group's ID. This is useful in scenarios where automated workflows need to manage group memberships dynamically, such as removing a bot or user from a chat group when certain conditions are met.

Practical examples include:

  • Automatically leaving a group after completing a task.
  • Managing group memberships based on user activity or status changes.
  • Integrating group management into larger automation pipelines.

Properties

Name Meaning
Server URL The full URL of your Evolution API server endpoint (e.g., https://api.exemplo.com).
API Key The API key credential required to authenticate requests to the Evolution API instance.
Nome Da Instância The name of the specific Evolution API instance you want to interact with.
ID Do Grupo The unique identifier (JID) of the group that you want to leave.

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to leave the specified group. The exact structure depends on the API's response but typically includes confirmation of the action or error details if the operation failed.

If the API returns any binary data (not indicated here), it would be summarized accordingly, but this operation primarily deals with JSON responses.

Dependencies

  • Requires access to the Evolution API via a valid server URL.
  • Requires an API key credential for authentication.
  • The node expects the Evolution API instance name to route the request correctly.
  • No additional external dependencies beyond standard HTTP requests.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API key will result in authentication errors.
    • Invalid or malformed group ID may cause the API to reject the request.
    • Wrong server URL or instance name can lead to connection failures or resource not found errors.

  • Error Messages:

    • "Operação não suportada." indicates that the requested operation is not implemented or recognized by the node.
    • Network or timeout errors suggest connectivity issues with the Evolution API server.

  • Resolutions:

    • Verify the API key and ensure it has the necessary permissions.
    • Double-check the group ID format and existence.
    • Confirm the server URL and instance name are correct and accessible.
    • Ensure the node parameters match the expected values for the "Grupo" resource and "Sair Do Grupo" operation.

Links and References

Discussion