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
Overview
This node enables sending WhatsApp contact cards through the Wassenger WhatsApp API. It is part of a broader integration that interacts with various WhatsApp messaging features. The "Send contacts" operation under the "Send messages" resource allows users to send one or multiple contact cards 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 during customer support conversations.
- Broadcasting contact cards to groups or channels for marketing or informational purposes.
- Automating the distribution of team or business contacts in WhatsApp workflows.
Practical example:
- A customer service chatbot sends a contact card of a sales representative to a user who requests more information.
- A company broadcasts updated contact details of its branches to a WhatsApp group of employees.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The target Wassenger Number ID used for message delivery. This identifies the WhatsApp account/device from which the message will be sent. |
| Target | Type of target chat to send the contacts to. Options: Phone (individual phone number), Group (WhatsApp group chat), Channel (broadcast channel). |
| 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 | List of contacts to send as contact cards. Minimum 1 and maximum 10 contacts per message. Each contact requires a phone number (E.164 format) and a name. |
| Options | Additional options for message delivery and behavior: - Priority: Normal, High, Low - Label: Custom label to categorize the message - Reference ID: Custom reference for tracking - Team Agent: Send on behalf of an agent - Live mode: Real-time sending without queue - Delivery Queue Mode: Controls queuing behavior - Maximum Retries: Number of retries for delivery - Chat Actions: Post-delivery actions like assigning chat, resolving, adding labels or metadata, etc. |
| Message Expiration | Defines time-to-live (TTL) for the message. Can specify expiration by seconds, duration string (e.g., "1h"), or specific date/time. |
| Mark Chat as Read | Boolean flag to notify WhatsApp that previous unread messages in the chat are read after delivery (blue double-check). Requires WhatsApp read confirmation enabled. |
| Typing simulation | Number of seconds (0-30) to simulate typing or recording status before sending the message. Zero disables simulation. |
| Quote Message | Message ID to quote when sending the contact card. Must be 18-32 hex characters and refer to a message in the same conversation. |
| Strict Message Order | Boolean to ensure messages are sent in strict order to the target chat. Useful for chatbots and 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 message IDs, status information, and any metadata returned by the Wassenger API confirming successful delivery or errors.
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 an API key credential for authenticating with the Wassenger WhatsApp API.
- The node depends on the Wassenger service being accessible and properly configured.
- Some properties load dynamic options via methods such as fetching available devices, groups, channels, labels, team agents, and departments, requiring proper API access rights.
- No additional environment variables beyond the API key credential are explicitly required.
Troubleshooting
- Invalid phone number format: The phone numbers must be in E.164 format (e.g., +1234567890). Errors occur if the format is incorrect. Ensure numbers match the regex pattern
/^\+[1-9]\d{1,14}$/. - Missing required fields: If the target type is phone, group, or channel, the corresponding ID or number must be provided; otherwise, the node will error.
- Exceeding contact limits: Sending more than 10 contacts at once is not allowed and will cause failure.
- Delivery failures due to rate limits: Using real-time mode or disabling queues while sending many messages rapidly may lead to bans or delivery failures. Use queue modes appropriately.
- Invalid agent or department IDs: When specifying team agents or departments for chat actions, IDs must be valid 24-character hexadecimal strings.
- Quote message errors: Quoting a message ID that does not exist in the same conversation or has invalid length/format will cause errors.
- Chat action misconfiguration: Providing incomplete parameters for chat actions (e.g., missing agent or department when required) will cause errors.
To resolve these issues:
- Validate all inputs carefully.
- Use the provided UI hints and validation rules.
- Follow WhatsApp and Wassenger best practices regarding message rates and queue usage.
- Check API permissions and credentials.