Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
Send messages → Send contacts
AI-generatedOverview
This node enables sending WhatsApp contact cards through the WaliChat WhatsApp API. It is designed to send one or multiple contacts (up to 10) as vCard-like messages to a specified WhatsApp chat target, which can be an individual phone number, a group chat, or a channel.
Common scenarios where this node is beneficial include:
- Sharing contact information with customers or team members directly via WhatsApp.
- Automating distribution of business contacts or support agents' details in customer service workflows.
- Broadcasting contact cards to groups or channels for marketing or informational purposes.
For example, a customer support automation could send a contact card of a support agent to a user requesting help, or a sales team could share product specialist contacts in a group chat.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The WaliChat Number ID used to send the message. This identifies the WhatsApp account/device from which the message will be sent. |
| Target | Type of target chat: Phone (individual), Group, or Channel. Determines how the message is routed. |
| Phone Number | The recipient's phone number in international E.164 format (e.g., +1234567890). Required if Target is Phone. |
| Group ID | The ID of the target WhatsApp group chat (e.g., 12345678902401234@g.us). Required if Target is Group. |
| Channel ID | The ID of the target WhatsApp channel (e.g., 12345678902402200@newsletter). Required if Target is Channel. |
| Contacts | A collection of contacts to send (minimum 1, maximum 10). Each contact includes: - Phone Number (E.164 format) - Contact Name (full name or display name) |
| Options | Additional options for message delivery and behavior: - Priority: Normal, High, Low - Label: Custom label to categorize the message - Reference ID: Custom reference string - Team Agent: Send on behalf of an agent - Live mode: Real-time sending without queue - Delivery Queue Mode: Default, Always Queue, Never Queue, Opportunistic - Maximum Retries: Number of retries for delivery - Chat Actions: Post-delivery actions like assigning chat, resolving, adding labels, setting metadata, etc. |
| Message Expiration | Defines time-to-live (TTL) for the message with options: - Seconds: expire after N seconds - Duration: expire after a duration string (e.g., 1h, 30m) - Date: expire at a specific date/time |
| Mark Chat as Read | Boolean flag to notify WhatsApp that previous unread messages are read after delivery (blue double-check). Requires WhatsApp privacy settings to allow read receipts. |
| Typing simulation | Number of seconds (0-30) to simulate typing or recording status before sending the message. 0 disables this feature. |
| Quote Message | Message ID to quote when sending this message (18-32 hex characters). Can only quote messages in the same conversation. |
| Strict Message Order | Boolean to ensure messages are sent in strict order to the target chat. Useful for chatbots or sequences. Not compatible with live mode or never queue delivery options. |
Output
The node outputs JSON data representing the result of the contact sending operation. This typically includes confirmation details such as message IDs, status, timestamps, or error information if the sending failed.
If binary data were involved (not applicable here), it would represent media files or attachments, but since this operation sends contact cards, output is purely JSON.
Dependencies
- Requires a valid API key credential for authenticating with the WaliChat WhatsApp API.
- The node depends on WaliChat services for device management, group/channel info, team agents, labels, departments, and message queueing.
- Proper configuration of the WaliChat API key in n8n credentials is necessary.
- The node uses dynamic loading methods to fetch devices, groups, channels, labels, team agents, and departments for dropdown selections.
Troubleshooting
- Invalid phone number format: The phone numbers must be in E.164 format (e.g., +1234567890). Errors occur if the regex validation fails. Ensure correct formatting.
- Missing required fields: Depending on the target type, either phone number, group ID, or channel ID must be provided.
- Agent or Department ID validation: When assigning chats or performing actions, agent and department IDs must be 24-character hexadecimal strings.
- Message delivery failures: If messages fail to send, check API key validity, network connectivity, and whether the target WhatsApp number is reachable.
- Live mode risks: Using real-time sending without queueing for high-volume messaging may lead to WhatsApp bans. Use queue modes appropriately.
- Quote message errors: Quoting requires the message ID to be valid and belong to the same conversation.
- Strict order incompatibility: Enabling strict message order cannot be combined with live mode or never queue options.