Evolution APIInstall

Overview

This node integrates with the Evolution API v2 to manage WhatsApp-related instances, messages, groups, chats, events, and integrations. It allows users to perform a wide range of operations such as creating and managing instances, sending various types of WhatsApp messages (text, images, videos, audio, documents, lists, buttons), managing groups, checking chat statuses, configuring webhooks, and setting up third-party integrations like Chatwoot.

A practical use case for this node is automating customer support workflows where you need to send messages or media to customers via WhatsApp, manage group chats, or integrate with external platforms like Chatwoot for enhanced communication management.

Specifically, for the Integração resource with the Chatwoot operation, the node configures Chatwoot integration by setting the Chatwoot URL and API token for a given instance.

Properties

For the Integração resource with Chatwoot operation, additional properties (not listed in your input but inferred from code) include:

Output

The node outputs a JSON array where each item corresponds to the result of an executed operation. The structure includes:

• success: Boolean indicating if the operation was successful.
• message (optional): A success message string.
• timestamp: ISO string timestamp of when the operation completed.
• Other fields depend on the specific API response returned by the Evolution API.

If the API returns data, it attempts to parse JSON strings into objects; arrays of results are also handled accordingly.

No binary data output is indicated in the provided code.

Dependencies

• Requires an API key credential for authenticating requests to the Evolution API.
• The node uses HTTP requests to the Evolution API endpoints.
• For Chatwoot integration, requires:
  • Chatwoot server URL.
  • Valid API token for Chatwoot.

These credentials and parameters must be configured within n8n.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication failures.
  • Incorrect instance names or parameters may lead to "not found" or similar errors from the API.
  • Malformed JSON in instance data or other JSON inputs can cause parsing errors.
  • Network connectivity issues to the Evolution API or Chatwoot server.

• Error messages:

  • Errors thrown by the node typically contain the API error message.
  • If the node is set to continue on fail, errors are returned as part of the output JSON with an error field.

• Resolutions:

  • Verify API keys and tokens are correctly set.
  • Ensure instance names and other parameters match those registered in the Evolution API.
  • Validate JSON inputs before running the node.
  • Check network access and firewall settings.

Links and References

• Evolution API documentation (assumed internal or provided by the API provider)
• Chatwoot official site: https://www.chatwoot.com/
• n8n documentation on HTTP Request and custom nodes: https://docs.n8n.io/

If you want details about other resources or operations, please provide their names.