Evolution APIInstall

Overview

This node integrates with the Evolution API v2, enabling automation and management of various messaging and communication tasks. It supports multiple resources such as instances, messages, groups, chats, events, and integrations. Specifically for the "Integração" (Integration) resource with the "Typebot" operation, it allows configuring the Typebot integration on a specified instance.

Common scenarios where this node is beneficial include:

• Automating WhatsApp message sending and management.
• Managing chat groups and participants.
• Setting up webhooks or external service integrations like Chatwoot, Evolution Bot, Typebot, Dify, and Flowise.
• Controlling instance lifecycle and connection states.

Practical example:

• Automatically configure a Typebot integration on a specific instance to enable chatbot interactions within your messaging platform.

Properties

(Note: For the "Integração" resource and "Typebot" operation, only the "Instance Name" property is required.)

Output

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

• success: Boolean indicating if the operation was successful.
• message: Optional descriptive message about the operation outcome.
• timestamp: ISO string timestamp when the operation was performed.
• Additional fields depend on the specific API response, e.g., details of created instances, sent messages, group info, or integration setup confirmation.

If the API returns an array of items, the output wraps them in an items array along with count and success flags.

The node does not explicitly handle binary data output.

Dependencies

• Requires an API key credential for authenticating requests to the Evolution API v2.
• The node uses HTTP requests to the Evolution API endpoints.
• Proper configuration of the Evolution API credentials in n8n is necessary.
• For the "Typebot" integration operation, the targeted instance must be accessible and properly configured to accept integration settings.

Troubleshooting

• Common issues:

  • Invalid or missing API authentication token can cause request failures.
  • Incorrect instance names may lead to "not found" errors.
  • Malformed JSON input for instance data or other parameters can cause parsing errors.
  • Network connectivity problems between n8n and the Evolution API server.

• Error messages:

  • Errors thrown by the API are caught and returned as error messages in the output if "Continue On Fail" is enabled.
  • Typical error messages include authentication failures, invalid parameters, or resource not found.

• Resolutions:

  • Verify that the API key credential is correctly set up and has proper permissions.
  • Double-check instance names and other identifiers.
  • Ensure JSON inputs are valid and well-formed.
  • Confirm network access to the Evolution API endpoint.

Links and References

• Evolution API documentation (assumed; no direct link provided in source)
• n8n documentation on creating custom nodes and using HTTP request helpers
• Typebot official site for understanding integration capabilities (external resource)

Note: This summary focuses on the "Integração" resource and "Typebot" operation as requested. Other resources and operations exist in the node but are outside this scope.