Evolution API icon

Evolution API

Interact with Evolution API

Overview

This node allows you to send WhatsApp contact information using the Evolution API. It is designed for scenarios where you need to programmatically share one or more contacts with a recipient via WhatsApp, such as in customer support workflows, CRM integrations, or automated onboarding processes.

Practical examples:

  • Sending a list of sales representatives' contacts to a customer.
  • Sharing technical support contact details automatically after a ticket is created.
  • Distributing business partner information to clients through WhatsApp.

Properties

Display Name Type Meaning
Nome Da Instância String (required) The name of the instance that will send the contact.
Número Do Destinatário String (required) The WhatsApp number of the recipient (destination).
Contatos Collection A list of contacts to send. Each contact includes:
- Nome Completo String (required) Full name of the contact.
- Número Do WhatsApp String (required) WhatsApp number (digits only, e.g., 559999999999).
- Número Formatado String (required) Formatted phone number (e.g., +55 99 9 9999-9999).
- Organização String (optional) Organization or company name.
- Email String (optional) Contact's email address.
- URL String (optional) Web page URL related to the contact.

Output

The output is a JSON array containing the result(s) of the contact sending operation. The structure typically reflects the response from the Evolution API and may include fields such as status, message ID, or error details if applicable.

Example output:

[
  {
    "status": "success",
    "messageId": "abc123",
    "details": "Contact sent successfully"
  }
]

Note: The exact output fields depend on the Evolution API's response.

Dependencies

  • External Service: Requires access to the Evolution API.
  • API Key/Credentials: You must configure valid Evolution API credentials in n8n under the name evolutionApi.
  • n8n Configuration: No additional environment variables are required beyond the credential setup.

Troubleshooting

  • Common Issues:

    • Missing or invalid credentials will prevent the node from working.
    • Incorrectly formatted phone numbers may cause the API to reject the request.
    • Required fields left empty (such as "Nome Da Instância" or "Número Do Destinatário") will result in errors.
  • Error Messages:

    • "Operação não suportada."
      This means the selected operation is not implemented for the chosen resource. Double-check your resource and operation selection.
    • API-specific errors (e.g., invalid contact data) will be returned in the output JSON; review the details for troubleshooting.

Links and References

Discussion