Evolution APIInstall

Overview

This node integrates with the Evolution API v2, enabling automation and management of various messaging and communication tasks related to WhatsApp-like instances. It supports operations on multiple resources such as instances, messages, groups, chats, events, and integrations.

Specifically, for the Integração (Integration) resource with the Evolution Bot operation, it configures the Evolution Bot integration for a specified instance. This allows users to connect their Evolution Bot service to an instance managed by the Evolution API, facilitating automated chatbot interactions or other bot-driven workflows.

Common scenarios where this node is beneficial include:

• Automating WhatsApp messaging workflows.
• Managing WhatsApp instances programmatically.
• Integrating third-party chatbots like Evolution Bot into WhatsApp instances.
• Sending various message types (text, images, videos, documents) through WhatsApp.
• Managing group chats and contacts.
• Setting up event webhooks and external integrations.

Example use case:

• A user wants to configure the Evolution Bot integration on a specific WhatsApp instance to enable automated customer support responses via the bot.

Properties

Output

The node outputs JSON data representing the result of the requested operation. The output structure varies depending on the operation but generally includes:

• success: Boolean indicating if the operation was successful.
• message: Optional descriptive message about the operation result.
• timestamp: ISO string timestamp when the operation was completed.
• Additional fields returned by the Evolution API relevant to the operation.

For the Evolution Bot integration operation, the output typically confirms the configuration status of the bot integration.

The node does not output binary data.

Dependencies

• Requires an API key credential for authenticating requests to the Evolution API v2.
• The node uses HTTP requests to communicate with the Evolution API endpoints.
• Proper configuration of the Evolution API credentials in n8n is necessary.
• The Evolution Bot service must be accessible and properly set up to accept integration configurations.

Troubleshooting

• Authentication errors: Ensure that the API key credential for the Evolution API is correctly configured and has sufficient permissions.
• Invalid instance name: Verify that the instance name provided exists and is correctly spelled.
• Network issues: Check network connectivity to the Evolution API endpoint.
• Malformed input data: For JSON inputs (e.g., instance data), ensure valid JSON format.
• API rate limits or downtime: If requests fail repeatedly, check for API rate limiting or service outages.

Common error messages may include authentication failures, resource not found, or invalid parameters. Resolving these usually involves verifying credentials, input parameters, and API availability.

Links and References

• Evolution API Documentation (hypothetical link as no direct URL provided)
• n8n HTTP Request Node Documentation
• WhatsApp Business API Overview

Note: Internal credential names and exact API endpoint details are abstracted for security and clarity.