Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

The node "Evolution API" provides an interface to interact with the Evolution API, allowing users to perform various operations on different resources. Specifically, for the resource Chat and operation Enviar Presença (Send Presence), the node sends a presence status (such as "typing" or "recording") to a specified contact in a chat instance. This is useful in scenarios where you want to simulate or indicate user activity in a chat application, such as showing that a message is being typed or audio is being recorded.

Practical examples include:

  • Indicating to a chat recipient that you are currently typing a message.
  • Showing that you are recording a voice note before sending it.
  • Automating presence signals in customer support chatbots to improve user experience.

Properties

Name Meaning
Nome Da Instância The name of the chat instance where the presence will be sent.
Contato The contact number (remote JID) to whom the presence status will be sent.
Presença The type of presence to send. Options: "Escrevendo..." (composing), "Gravando..." (recording).
Delay Duration in milliseconds for which the presence status remains active before stopping.

Output

The node outputs a JSON array containing the result of the presence sending operation. The exact structure depends on the Evolution API response but generally confirms whether the presence was successfully sent or if there were any errors.

If the node supports binary data output, it is not indicated in the provided code or properties, so the output is purely JSON-based.

Dependencies

  • Requires an API key credential for authenticating with the Evolution API.
  • The base URL for requests is https://doc.evolution-api.com/api-reference.
  • Proper configuration of the API authentication in n8n credentials is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect contact numbers or instance names may lead to errors or no effect.
    • Sending presence without specifying required fields will throw validation errors.

  • Error messages:

    • "Operação não suportada." indicates that the selected operation is not implemented for the chosen resource.
    • Network or API errors will typically return standard HTTP error messages; ensure the API endpoint is reachable and credentials are valid.

  • Resolutions:

    • Verify all required input properties are correctly filled.
    • Check API credentials and permissions.
    • Confirm the contact number format matches expected standards.

Links and References

Discussion