WaAPI icon

WaAPI

Interact with WaAPI API

Actions83

Overview

This node operation allows sending a geographic location message to a specified chat via the WaAPI service. It is useful for automating the sharing of precise locations in messaging workflows, such as notifying a contact or group about a meeting point, delivery address, or event location.

Practical examples include:

  • Sending a customer's delivery location to a driver.
  • Sharing a meetup spot with a group chat.
  • Automatically sending a location update based on GPS data from another system.

Properties

Name Meaning
Id The ID of the WaAPI instance to use for sending the message.
Chat Id The target chat identifier where the location will be sent. Format: <countrycode><number>@c.us for individuals or @g.us for groups.
Latitude Latitude coordinate of the location to send.
Longitude Longitude coordinate of the location to send.
Options Additional JSON options for the location message, including:
- name: Name of the location (e.g., "Googleplex")
- address: Full address string
- url: Optional URL related to the location

Output

The node outputs JSON data representing the response from the WaAPI service after attempting to send the location message. This typically includes confirmation details such as message ID, status, and any metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the WaAPI service via an API key credential configured in n8n.
  • The node uses the WaAPI REST API endpoint at https://waapi.app/api/v1.
  • Proper authentication headers must be set using the provided API key credential.

Troubleshooting

  • Invalid Chat Id format: Ensure the chat ID follows the correct pattern (<countrycode><number>@c.us for individual chats or @g.us for groups). Incorrect formats will cause message sending failures.
  • Authentication errors: Verify that the API key credential is correctly configured and has not expired.
  • Missing required fields: All required properties (Id, Chat Id, Latitude, Longitude) must be provided; otherwise, the node will throw validation errors.
  • Network issues: Connectivity problems with the WaAPI endpoint can cause timeouts or failed requests.
  • Malformed JSON in Options: If the Options field contains invalid JSON, parsing will fail. Make sure it is valid JSON.

Links and References

Discussion