Evolution API icon

Evolution API

Interact with Evolution API

Actions64

Overview

This node, named "Evolution API," is designed to interact with the Evolution API service. Specifically, for the Resource "Chat" and Operation "Read Messages," it allows users to retrieve a specific chat message from a contact by providing identifying details such as the instance name, contact number, and message ID. This functionality is useful in scenarios where you need to fetch and process individual chat messages programmatically, for example, to analyze message content, verify message status, or integrate chat data into other workflows.

Properties

Name Meaning
Name Da Instância The name of the instance from which to read the message.
Contato The contact's phone number associated with the chat message.
Message ID The unique identifier of the message to be read.
Mensagem É Minha Boolean flag indicating if the message was sent by the instance (true) or received (false).

Output

The node outputs a JSON array containing the retrieved message data. Each item in the output array represents a single message object with its properties as returned by the Evolution API. The exact structure depends on the API response but typically includes message metadata such as sender, timestamp, content, and status.

There is no indication that this node outputs binary data.

Dependencies

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

Troubleshooting

  • Unsupported Operation Error: If you select an operation not supported by the node, it will throw an error stating the operation is not supported. Ensure you use only valid resource-operation combinations.
  • Missing Required Parameters: All input properties marked as required must be provided; otherwise, the node may fail or return incomplete data.
  • API Authentication Issues: Invalid or missing API credentials will cause authentication failures. Verify that the API key or token is correctly configured.
  • Incorrect Contact or Message ID: Providing wrong contact numbers or message IDs will result in no data found or errors from the API. Double-check these values before execution.

Links and References

Discussion