Evolution API Direct icon

Evolution API Direct

Interact with Evolution API using direct URL and API Key
Join our community

Actions64

Overview

The node "Evolution API Direct" 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. Specifically, for the Resource "Instancia" and Operation "Definir Presença" (Set Presence), this node sets the presence status of a given instance in the Evolution system. This is useful in scenarios where you want to programmatically update the availability status of an instance, for example marking it as "available" or "unavailable" based on external triggers or workflows.

Practical examples include:

  • Automatically setting an instance's presence to "available" during business hours.
  • Marking an instance as "unavailable" when maintenance is scheduled or detected.
  • Integrating presence status updates into broader automation workflows that depend on instance availability.

Properties

Name Meaning
Server URL The full URL of your Evolution API endpoint (e.g., https://api.exemplo.com).
API Key The API key credential used to authenticate requests to the Evolution API.
Nome Da Instância The name of the instance whose presence status you want to set.
Presença The presence status to assign to the instance. Options: "Disponível" (available), "Indisponível" (unavailable).

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to set the presence status. The exact structure depends on the API response but typically includes confirmation of the updated presence state or error details if the operation failed.

No binary data output is indicated.

Dependencies

  • Requires access to the Evolution API endpoint specified by the user.
  • Requires a valid API key credential for authentication.
  • The node expects the user to provide the correct server URL and instance name.
  • No additional external dependencies beyond standard HTTP request capabilities.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API key will cause authentication failures.
    • Invalid server URL or network issues can prevent successful API calls.
    • Providing an incorrect instance name may result in errors or no effect.
    • Unsupported operations or resources will throw an error indicating the operation is not supported.

  • Error Messages:

    • "Operação não suportada." means the selected operation is not implemented for the chosen resource. Verify that the resource and operation names are correct.
    • API errors returned from the Evolution API will be passed through; check the API documentation for specific error codes and messages.

  • Resolutions:

    • Double-check API key validity and permissions.
    • Ensure the server URL is reachable and correctly formatted.
    • Confirm the instance name exists and is spelled correctly.
    • Use only supported resource-operation combinations.

Links and References

Discussion