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 location
AI-generatedOverview
This node allows sending a location message via WhatsApp using the WaliChat API. It supports specifying the target chat by phone number, group ID, or channel ID and lets users send either an address or geographic coordinates as the location. This is useful for scenarios such as sharing meeting points, delivery addresses, event locations, or any place of interest directly within WhatsApp conversations.
Practical examples include:
- Sending a customer's delivery address to a support agent.
- Sharing a meetup spot with a group chat.
- Broadcasting a location update to a channel audience.
Properties
| Name | Meaning |
|---|---|
| WhatsApp number | The WaliChat Number ID used to send the message. |
| Target | Type of target chat: Phone (individual), 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 group chat (e.g., 12345678902401234@g.us). Required if Target is Group. |
| Channel ID | ID of the target channel (e.g., 12345678902402200@newsletter). Required if Target is Channel. |
| Location Type | How to specify the location: Address or Coordinates. |
| Address | The textual address of the location (3-100 characters). Required if Location Type is Address. |
| Latitude | Latitude coordinate (-90 to 90). Required if Location Type is Coordinates. |
| Longitude | Longitude coordinate (-180 to 180). 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) - Real-time sending mode toggle - Delivery queue mode - Maximum retries - Post-delivery chat actions (assign, resolve, label, metadata) |
| Message Expiration | Defines time-to-live (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 delivery (blue double-check). |
| Typing simulation | Seconds to simulate typing or recording status before sending (0 disables). Range 2-30 seconds. |
| Quote Message | Message ID to quote when sending this location message (must be in same conversation). |
| Strict Message Order | Boolean to ensure messages are sent in strict order. Useful for chatbots or sequences. Not compatible with live or never-queue modes. |
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 operation failed.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the WaliChat WhatsApp API.
- The node depends on WaliChat services for sending messages, managing groups, channels, labels, agents, and other related entities.
- Proper configuration of the WaliChat API key in n8n credentials is necessary.
- Some properties load dynamic options from WaliChat endpoints (e.g., devices, groups, channels, team agents, labels).
Troubleshooting
- Invalid phone number format: Ensure phone numbers follow the E.164 format (e.g., +1234567890). The node validates this with a regex.
- Missing required fields: Depending on the target type, ensure the corresponding ID or phone number is provided.
- Message delivery failures: Could be due to invalid device ID, network issues, or WhatsApp restrictions. Check API key validity and quota.
- Live mode risks: Using real-time sending without queuing at high volume may lead to WhatsApp bans. Use queue modes appropriately.
- Strict order conflicts: Enabling strict message order is incompatible with live or never-queue delivery modes.
- Quoted message errors: Quoting requires the message ID to be valid and belong to the same conversation.
- Agent or department IDs: Must be valid 24-character hexadecimal strings; otherwise, post-delivery chat actions will fail.
Links and References
- WaliChat API Documentation (general reference for API capabilities)
- WhatsApp Business API Guidelines (for understanding message types and limits)
- E.164 Phone Number Format