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 with the Evolution API by specifying a direct server URL and an API key for authentication. It supports various resources and operations, including sending chat presence updates. This node is useful in scenarios where you want to programmatically notify a contact about your current chat status, such as indicating when you are typing or recording a voice message.

A practical example is integrating this node into a workflow that manages customer support chats, where it can send real-time presence updates ("typing..." or "recording...") to contacts to improve communication transparency.

Properties

Name Meaning
Server URL The full URL of your Evolution API server (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.
Contato The contact number (remote JID) to whom the presence update will be sent.
Presença The type of presence to send; options are: "Escrevendo..." (composing) or "Gravando..." (recording).
Delay The duration in milliseconds that the presence status should remain active before clearing.

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to send the presence update. The exact structure depends on the API's response but generally includes confirmation of the presence status sent or error details if the operation failed.

No binary data output is involved in this operation.

Dependencies

  • Requires access to an Evolution API server reachable via the provided Server URL.
  • Needs a valid API key credential for authentication.
  • Proper configuration of the instance name corresponding to the Evolution API instance.
  • Network connectivity to the Evolution API endpoint.

Troubleshooting

  • Common Issues:

    • Incorrect Server URL or unreachable API endpoint may cause connection failures.
    • Invalid or expired API key will result in authentication errors.
    • Providing an incorrect contact number format might lead to failure in sending presence.
    • Specifying an unsupported presence type or invalid delay value could cause unexpected behavior.

  • Error Messages:

    • "Operação não suportada." indicates that the selected operation is not supported for the chosen resource. Verify that "Enviar Presença" is correctly selected under the "Chat" resource.
    • Authentication errors typically suggest issues with the API key; ensure it is correct and has necessary permissions.
    • Timeout or network errors imply connectivity problems; check network settings and API availability.

Links and References

Discussion