Actions6
Overview
This node integrates with the Uadezap API to send various types of messages, including text, images, audio, documents, videos, and locations. Specifically, the Send Location operation allows users to send a geographic location to a specified phone number. This is useful in scenarios such as sharing meeting points, delivery addresses, or any place coordinates directly via messaging.
Practical examples:
- A delivery service sending the exact drop-off location to a customer.
- Event organizers sharing venue locations with attendees.
- Friends sharing their current location for meetups.
Properties
| Name | Meaning |
|---|---|
| Number | Phone number to which the location will be sent (e.g., "5522999999999"). |
| Latitude | Latitude coordinate of the location to send (required). |
| Longitude | Longitude coordinate of the location to send (required). |
| Name | Optional name of the location (e.g., "Central Park"). |
| Address | Optional address description of the location (e.g., "5th Avenue, New York, NY"). |
Output
The node outputs JSON data representing the response from the Uadezap API after attempting to send the location message. The structure typically includes confirmation details such as message status, IDs, timestamps, or error information if the request failed.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Uadezap API.
- An API key credential must be configured in n8n to authenticate requests.
- The base URL for the API is taken from the credential configuration.
Troubleshooting
- Invalid phone number format: Ensure the phone number is in the correct international format without spaces or special characters.
- Missing required fields: Latitude, longitude, and number are mandatory; missing these will cause errors.
- API authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Network issues: Check connectivity to the Uadezap API endpoint.
- Error responses from API: Review the returned error message for details; common issues include invalid coordinates or rate limits.
Links and References
- Uadezap API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes