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 a location message via WhatsApp using the Wassenger API. It supports specifying the target chat by phone number, group ID, or channel ID and allows sending location either by address or geographic coordinates. This is useful for scenarios such as sharing meeting points, event locations, or delivery addresses directly within WhatsApp conversations.
Practical examples:
- A delivery service sends the exact drop-off location to a customer.
- An event organizer shares the venue address with attendees in a group chat.
- A support agent sends a store location to a customer via a WhatsApp channel.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The Wassenger Number ID used to send the message (select from available devices). |
| Target | Type of target chat: Phone, Group, or Channel. |
| Phone Number | Target phone number in international E.164 format (e.g., +1234567890). Required if Target is Phone. |
| Group ID | ID of the target WhatsApp group chat (e.g., 12345678902401234@g.us). Required if Target is Group. |
| Channel ID | ID of the target WhatsApp channel (e.g., 12345678902402200@newsletter). Required if Target is Channel. |
| Location Type | How to specify the location: Address or Coordinates. |
| Address | The physical address string (3-100 characters) to send as location. Required if Location Type is Address. |
| Latitude | Latitude coordinate (-90 to 90) for location. Required if Location Type is Coordinates. |
| Longitude | Longitude coordinate (-180 to 180) for location. Required if Location Type is Coordinates. |
| Location Name | Optional name or description for the location (up to 100 characters). |
| Options | Collection of optional settings including: - Priority (Normal, High, Low) - Label (custom categorization) - Reference ID - Team Agent (send on behalf of an agent) - Live mode (real-time sending) - Delivery queue mode (default, always queue, never queue, opportunistic) - Maximum retries - Chat actions after delivery (assign, resolve, label, metadata, etc.) |
| Message Expiration | Define TTL for the message with options to expire after seconds, duration (e.g., "1h"), or specific date/time. |
| Mark Chat as Read | Boolean to notify WhatsApp that previous unread messages will be marked as read after this message is delivered (blue double-check). |
| Typing simulation | Seconds (0-30) to simulate typing or recording status before sending the message. Set 0 to disable. |
| Quote Message | Message ID to quote when sending this location message (must be 18-32 hex characters and in the same conversation). |
| Strict Message Order | Boolean to ensure messages are sent in strict order. Useful for chatbots or sequences. Not compatible with live mode or never queue delivery. |
Output
The node outputs JSON data representing the result of the location message sending operation. This typically includes confirmation details such as message IDs, status, timestamps, or error information if the sending failed.
No binary data output is involved.
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 (e.g., devices, groups, channels, labels, team agents) which require appropriate permissions and API access.
- Proper WhatsApp number provisioning and configuration in Wassenger is necessary.
Troubleshooting
- Invalid phone number format: Ensure the phone number is in E.164 format (e.g., +1234567890). The node validates this with a regex.
- Missing required fields: Depending on the target type, ensure the corresponding field (phone, groupId, or channel) is provided.
- API authentication errors: Verify the API key credential is valid and has sufficient permissions.
- Message delivery failures: Check the priority, queue mode, and retry settings. Using real-time mode with high message volume may cause bans or throttling.
- Typing simulation issues: Setting typing simulation too long may delay message sending unnecessarily.
- Quote message errors: Quoting a message not in the same conversation or with invalid ID length will fail.
- Strict order conflicts: Using strict message order together with live mode or never queue delivery is incompatible and may cause errors.