Evolution API

Overview

This node interacts with the Evolution API to send group invitation links. Specifically, for the "Grupo" resource and the "Enviar Link De Convite" operation, it sends an invitation link message to specified recipients for a given group instance. This is useful in scenarios where you want to automate inviting multiple users to join a group by sending them a customized invite link via messaging.

Practical examples include:

• Automatically inviting new members to a community or team chat group.
• Sending batch invitations to customers or event participants to join a dedicated group.
• Integrating group invitation workflows into CRM or marketing automation systems.

Properties

Output

The node outputs a JSON array containing the response from the Evolution API after attempting to send the invitation link(s). Each item in the output corresponds to the result of the send operation, typically including status information or confirmation details.

If the API supports binary data (not indicated here), it would be summarized accordingly, but this node primarily deals with JSON responses.

Dependencies

• Requires an API key credential for authenticating with the Evolution API.
• The node expects proper configuration of this API authentication within n8n credentials.
• Network access to the Evolution API endpoint is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials can cause authentication failures.
  • Incorrect group ID or instance name may lead to errors indicating the group or instance was not found.
  • Malformed recipient numbers (wrong format or missing country code) can cause delivery failures.
  • Exceeding rate limits or quota restrictions on the Evolution API might result in temporary blocks.

• Error messages:

  • "Operação não suportada." indicates the requested operation is not implemented or recognized; verify the selected resource and operation.
  • API error responses usually contain descriptive messages; check these for clues about invalid parameters or permission issues.

• Resolutions:

  • Double-check all input properties for correctness and completeness.
  • Ensure the API key credential is valid and has required permissions.
  • Format recipient numbers correctly with country codes and commas separating multiple entries.
  • Review API usage limits and adjust request frequency if needed.

Links and References

• Evolution API official documentation (refer to your API provider's docs for detailed info)
• n8n documentation on creating and using API credentials
• Best practices for phone number formatting in international contexts