Actions50
- Message Actions
- Contact Actions
- Account Actions
- Call Actions
- Chat Actions
- Group Actions
- Instance Actions
- Media Actions
- Session Actions
- User Actions
Overview
This node enables sending a contact card via WhatsApp using the WSAPI WhatsApp API. It is designed to share a contact's information (name and phone number) with a specified WhatsApp user or group. This functionality is useful in scenarios such as customer support, team collaboration, or personal communication where sharing contact details quickly within a chat is needed.
Practical examples:
- A support agent sends a colleague’s contact info to a customer for follow-up.
- A team member shares a new client’s contact details in a group chat.
- Automatically sending a business contact card after a user interaction in a chatbot flow.
Properties
| Name | Meaning |
|---|---|
| To | The WhatsApp ID of the recipient. For individual contacts, this is the phone number followed by @s.whatsapp.net (e.g., 1234567890@s.whatsapp.net). For groups, it is the group ID followed by @g.us. |
| Contact Name | Full name of the contact to be shared. This will appear as the display name in WhatsApp when the contact card is received. |
| Contact Phone | Phone number of the contact to share, including country code but without the + symbol (e.g., 1234567890). |
| Advanced Options | Additional optional settings: - Mentions: Comma-separated list of phone numbers (without @) to mention in the message.- Reply To Message ID: ID of a message to reply to. - Is Forwarded: Boolean flag indicating if the message is forwarded. - View Once: (Not applicable for sendContact operation; applies only to media messages.) |
Output
The node outputs JSON data representing the result of the send contact operation. This typically includes metadata about the sent message such as message ID, status, timestamps, and any relevant response from the WhatsApp API confirming the message delivery.
No binary data output is expected for this operation since it deals with contact cards (structured text data).
Dependencies
- Requires an active connection to the WSAPI WhatsApp API service.
- Needs an API key credential configured in n8n to authenticate requests to the WSAPI endpoint.
- The base URL for the WSAPI must be set in the credentials configuration.
- Proper permissions on the WhatsApp account linked to the API are necessary to send messages.
Troubleshooting
- Invalid "To" format: Ensure the recipient ID follows the correct format (
phone@s.whatsapp.netfor individuals,group@g.usfor groups). Missing country codes or incorrect suffixes will cause errors. - Missing required fields: The node requires
Contact NameandContact Phoneto be provided. Omitting these will result in validation errors. - Authentication errors: Verify that the API key credential is valid and has not expired.
- Message sending failures: Could be due to network issues, WhatsApp API limits, or restrictions on the recipient side (e.g., blocked contacts).
- Reply To Message ID invalid: If replying to a message, ensure the message ID exists and belongs to the same chat.