Actions64
- Instance Actions
- Message Actions
- Group Actions
- Integration Actions
- Chat Actions
- Profile Actions
- Event Actions
Overview
The node "Evolution API" allows interaction with the Evolution API service. Specifically, for the Resource "Message" and Operation "Send Contact," it sends one or multiple contact cards to a specified recipient via WhatsApp. This is useful in scenarios where you want to share contact information programmatically, such as sending customer support contacts, sales leads, or team member details directly through WhatsApp messages.
Practical examples include:
- Automatically sending a list of company representatives' contact cards to new clients.
- Sharing event organizer contacts with attendees.
- Distributing emergency contact information to a group.
Properties
| Name | Meaning |
|---|---|
| Instance Name | The name of the instance that will send the contact. |
| Recipient Number | The WhatsApp number of the message recipient (in string format). |
| Contacts | A list of contacts to send. Each contact includes: |
| - Full Name | Full name of the contact. |
| - WhatsApp Number | WhatsApp number of the contact (numbers only, e.g., 559999999999). |
| - Formatted Number | Formatted phone number (e.g., +55 99 9 9999-9999). |
| - Organization | Name of the organization or company associated with the contact. |
| Email address of the contact. | |
| - URL | URL of the contact's webpage or profile. |
Output
The node outputs a JSON array containing the result of the send contact operation. Each element corresponds to the response from sending the contact(s) to the specified recipient. The exact structure depends on the Evolution API response but generally confirms success or failure of the message delivery.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Evolution API service.
- Needs an API authentication credential configured in n8n (an API key or token).
- The base URL for requests is
https://doc.evolution-api.com/api-reference. - Proper configuration of the "Instance Name" to identify the sending instance.
Troubleshooting
Common issues:
- Invalid or missing recipient number format may cause message sending failures.
- Incorrect or incomplete contact details can lead to partial or failed contact card delivery.
- Authentication errors if the API key/token is invalid or missing.
- Unsupported operations or resources will throw an error indicating the function is not supported.
Error messages:
"Operation not supported."— Occurs if the selected resource-operation combination is not implemented.- API errors related to authentication or request validation will be returned by the Evolution API and surfaced by the node.
Resolutions:
- Verify all required fields are correctly filled.
- Ensure the API credentials are valid and have necessary permissions.
- Confirm the recipient number and contact numbers follow the expected formatting rules.
- Check the Evolution API documentation for any changes or additional requirements.
Links and References
- Evolution API Documentation (official API reference)
- WhatsApp contact card format guidelines (refer to WhatsApp Business API docs for contact message structure)