Evolution API icon

Evolution API

Interact with Evolution API

Overview

The node "Evolution API" provides integration with the Evolution API service, allowing users to perform various operations on different resources. Specifically, for the Chat resource and the Gestionar Archivo (Manage Archive) operation, this node enables users to archive or unarchive chat conversations by specifying details such as the contact number, message ID, and whether the message was sent by the instance.

This node is beneficial in scenarios where automated management of chat archives is needed, such as organizing conversations, cleaning up active chats, or restoring archived chats for review. For example, a user can automate archiving old conversations or unarchiving important ones based on certain triggers or workflows.

Properties

Name Meaning
Nombre De La Instancia The name of the instance performing the operation; identifies which instance is used.
Contacto The phone number or identifier of the contact whose conversation will be archived/unarchived.
Acción Choose between "Archivar" (archive) or "Desarchivar" (unarchive) the conversation.
ID Del Mensaje The ID of the last message in the conversation, used to identify the specific chat thread.
El Mensaje Es Mío Boolean indicating if the message was sent by the instance itself (true) or not (false).

Output

The node outputs a JSON array containing the result of the archive management operation. The exact structure depends on the Evolution API response but generally includes confirmation of the archive status change for the specified chat conversation.

No binary data output is indicated for this operation.

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 within n8n credentials is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect or missing required parameters (e.g., contact number, message ID) will lead to errors from the API.
    • Attempting to archive/unarchive unsupported or non-existent conversations may return errors.
  • Error Messages:

    • "Operação não suportada." indicates that the selected operation is not supported for the chosen resource. Verify that the resource and operation names are correct.
    • API errors related to invalid parameters should be resolved by ensuring all required fields are correctly filled.
    • Network or connectivity issues may cause request failures; verify internet access and API endpoint availability.

Links and References

Discussion