Actions28
- Messages Actions
- Media Actions
- Templates Actions
- Contacts Actions
- Analytics Actions
- Webhooks Actions
Overview
This node enables sending a location message via WhatsApp using the WhatsApp Business API. It allows workflows to share geographic coordinates along with optional descriptive information such as a location name and address. This is useful in scenarios like customer support, delivery tracking, event invitations, or any case where sharing a precise location is needed.
For example, a business can automatically send a customer's current location to a support agent, or a delivery service can notify customers of the driver's location by sending a location message.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The recipient's phone number in international format (e.g., 5511999999999). |
| Latitude | The latitude coordinate of the location to send. |
| Longitude | The longitude coordinate of the location to send. |
| Location Name | Optional name or title for the location (e.g., "Central Park"). |
| Location Address | Optional detailed address or description of the location. |
Output
The node outputs JSON data representing the response from the WhatsApp API after sending the location message. This typically includes message status details confirming whether the message was sent successfully or any error information if it failed.
No binary data output is produced by this operation.
Dependencies
- Requires an active subscription and valid API key credential for the external WhatsApp API service.
- Needs proper configuration of credentials within n8n for authentication.
- Relies on the external WhatsApp Business API endpoint provided by the integrated service.
Troubleshooting
- Invalid Subscription or API Key: If the API key or subscription is invalid, the node throws an error indicating invalid credentials. Verify that the API key is correct and the subscription is active.
- Incorrect Phone Number Format: Ensure the phone number is in the international format without spaces or special characters.
- Missing Required Parameters: Latitude, longitude, and phone number are required. Omitting these will cause errors.
- API Rate Limits or Service Downtime: Temporary failures may occur due to rate limits or service issues; retrying later might resolve these.
- JSON Parsing Errors: Although not directly relevant here, other operations use JSON parameters; ensure JSON inputs are well-formed.