Actions12
- Sesiones Actions
- Mensajería Actions
- Chats y Mensajes Actions
Overview
This node allows sending a location message through a messaging API. It is useful for scenarios where you want to share geographic coordinates with a chat contact or group, such as sharing your current position, a meeting point, or any place of interest.
Practical examples include:
- Sending your current GPS location to a friend.
- Sharing the location of an event or venue in a chat.
- Providing directions by sending a specific latitude and longitude.
Properties
| Name | Meaning |
|---|---|
| ID del Chat | The identifier of the chat where the location will be sent (e.g., phone number with suffix). |
| Latitud | Latitude coordinate of the location to send (decimal number). |
| Longitud | Longitude coordinate of the location to send (decimal number). |
| Título de la Ubicación | A title or label for the location being sent (optional descriptive text). |
| Responder a Mensaje | Optional ID of a message to which this location message should reply. |
Output
The node outputs a JSON object representing the response from the messaging API after attempting to send the location. This typically includes confirmation details about the sent message, such as message ID, status, or error information if the operation failed.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the external messaging API service.
- The node uses HTTP requests to communicate with
https://api.expertosenia.com. - The session name can be configured; defaults to
"default"if not specified.
Troubleshooting
Common issues:
- Invalid or missing chat ID may cause the message not to send.
- Incorrect latitude or longitude values (out of valid range) might result in errors.
- Missing or invalid API key credential will prevent authentication.
- Reply-to message ID that does not exist or is invalid may cause the API to reject the request.
Error messages:
- Errors returned from the API are included in the output JSON under an
errorfield whencontinueOnFailis enabled. - Typical error messages relate to authorization failures, invalid parameters, or network issues.
- Errors returned from the API are included in the output JSON under an
Resolution tips:
- Verify the chat ID format matches the expected pattern.
- Ensure latitude is between -90 and 90, longitude between -180 and 180.
- Confirm the API key credential is correctly set up in n8n.
- Use valid message IDs for replying to existing messages.