Actions6
- Send Message Actions
Overview
This node integrates with a WhatsApp messaging API to send location messages to specified recipients. It is designed for scenarios where you want to share geographic locations via WhatsApp, such as sending meeting points, delivery addresses, or event locations directly through automated workflows.
Practical examples include:
- Sending a customer's delivery location to a driver.
- Sharing a meeting place with a group of contacts.
- Automatically notifying users of an event venue location.
Properties
| Name | Meaning |
|---|---|
| Recipient | The phone number of the message recipient, including country code (e.g., 5531900000000). |
| Delay | Optional delay in milliseconds before sending the message (e.g., 1200 ms). |
| Presence | Status indicator while sending the message; options: Available, Composing, Empty, Paused, Recording, Unavailable. |
| Location Name | Optional name or label for the location being sent (e.g., "Central Park"). |
| Address | Optional address description associated with the location. |
| Latitude | Required latitude coordinate of the location to send. |
| Longitude | Required longitude coordinate of the location to send. |
Output
The node outputs JSON data representing the result of the location message send operation. This typically includes confirmation details from the WhatsApp API about the message status, such as message ID, timestamp, and delivery status.
If binary data were involved (e.g., media files), it would be summarized here, but this node focuses on sending location data only.
Dependencies
- Requires an API key credential for authenticating with the WhatsApp API service.
- Needs configuration of the base URL for the WhatsApp API instance.
- The node uses HTTP POST requests to send location messages to the endpoint
/message/sendLocation/{instanceName}/.
Troubleshooting
- Invalid Phone Number: Ensure the recipient number includes the correct country code and no extra characters.
- Missing Coordinates: Latitude and longitude are required; missing these will cause errors.
- API Authentication Errors: Verify that the API key credential is correctly configured and has necessary permissions.
- Delay Misconfiguration: Delay should be a non-negative integer representing milliseconds; invalid values may cause unexpected behavior.
- Presence Option Issues: Use one of the predefined presence statuses; invalid values might be ignored or cause errors.
Common error messages usually relate to authentication failures, invalid input data, or network issues. Checking credentials, input validation, and network connectivity can resolve most problems.
Links and References
- WhatsApp Location Message API documentation (refer to your WhatsApp API provider's official docs).
- n8n documentation on creating and configuring custom nodes.
- General best practices for phone number formatting in international contexts.