Evolution API icon

Evolution API

Complete WhatsApp automation with Evolution API
Join our community

Actions48

Overview

This node enables sending a location message via WhatsApp using the Evolution API. It is designed to automate the process of sharing geographic coordinates with a specified contact on WhatsApp. This can be particularly useful in scenarios such as:

  • Sharing your current location with friends or family automatically.
  • Sending meeting points or event locations in customer support or sales workflows.
  • Integrating location-based notifications or alerts into business processes.

For example, you could use this node to send a location pin to a client with directions to a store or office, triggered by an event in your workflow.

Properties

Name Meaning
Phone Number The recipient's phone number including country code, without the "+" sign (e.g., 5511999999999).
Latitude The latitude coordinate of the location to send.
Longitude The longitude coordinate of the location to send.
Additional Fields Optional extra settings:
- Delay: Time in milliseconds to wait before sending the message.
- Link Preview: Enable or disable link preview in messages (boolean).
- Quoted Message ID: ID of a message to quote or reply to.
- Mentions: Comma-separated list of phone numbers to mention in the message.

Output

The node outputs a JSON object containing the response from the Evolution API after attempting to send the location message. This typically includes details about the message status and any metadata returned by the API.

If the operation fails and "Continue On Fail" is enabled, the output will contain an error message describing the failure.

No binary data is output by this node for the Send Location operation.

Dependencies

  • Requires valid credentials for the Evolution API, including:

    • Base URL of the API.
    • API key for authentication.
    • Instance name identifying the WhatsApp instance.

  • Optionally uses credentials for an auxiliary API service ("N8N Tools API") for subscription validation.

  • The node makes HTTP POST requests to the Evolution API endpoints to perform actions.

Troubleshooting

  • Invalid Credentials: If the API key or instance name is incorrect, the node will fail. Ensure that the credentials are correctly configured and active.

  • Subscription Validation Failure: The node validates the subscription via an external API. Errors like 401 or 403 indicate invalid subscription or API key. Check your subscription status and API keys.

  • Unknown Operation or Resource: If an unsupported operation or resource is selected, the node throws an error indicating the unknown operation/resource.

  • Message Sending Delays: If using the delay option, ensure the delay value is reasonable to avoid unintended long waits.

  • Phone Number Format: The phone number must include the country code but no "+" sign. Incorrect formatting may cause message delivery failures.

Links and References

Discussion