CHACHAT Chat Location Node

Node for sending location data via Chat API

Overview

This node, named "CHACHAT Chat Location Node," is designed to send location data via a chat API. It allows users to provide geographic coordinates (latitude and longitude) along with an address and a phone number to which the location information will be sent. This node is useful in scenarios where automated sharing of location details through a chat service is required, such as notifying a contact about a meeting place, sharing delivery locations, or providing real-time position updates.

Practical examples include:

  • Sending a customer's delivery location to a driver via chat.
  • Sharing event venue details with participants automatically.
  • Notifying emergency contacts with precise location data.

Properties

Name Meaning
Phone Number The phone number for the Chat API to which the location data is sent.
Latitude The latitude coordinate of the location to share.
Longitude The longitude coordinate of the location to share.
Address The textual address corresponding to the location coordinates.

Output

The node outputs JSON data containing the response from the chat API after sending the location. This typically includes confirmation or status information returned by the API regarding the message delivery.

If multiple input items are processed, the output corresponds to the first successful API response. If all fail and continueOnFail is enabled, it returns the original input data unchanged.

No binary data output is produced by this node.

Dependencies

  • Requires an external chat API service accessible via HTTP POST requests.
  • Needs credentials including:
    • A base URL for the chat API endpoint.
    • An authentication token (used as a Bearer token in the Authorization header).
    • A session identifier.
  • Uses the Axios library for HTTP requests.
  • The node expects these credentials to be configured in n8n prior to execution.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect phone numbers or malformed location data may result in API errors.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:
    • Authentication errors typically indicate invalid tokens or sessions; verify credential correctness.
    • API response errors may include validation messages if required fields are missing or incorrect.
    • If the node throws an error referencing item index, it indicates which input caused the failure.
  • To resolve errors, ensure all required properties are correctly set, credentials are valid, and the chat API service is reachable.

Links and References

  • Axios HTTP client documentation
  • Refer to your chat API provider's official documentation for details on the /v1/send/location endpoint and required parameters.

Discussion