CrunchzApp icon

CrunchzApp

Interact with CrunchzApp API
Join our community

Actions22

Overview

This node allows sending a geographic location message to a specified contact via the CrunchzApp API. It is useful in scenarios where you want to share precise location information, such as meeting points, event venues, or delivery addresses, directly through messaging.

For example, a user can send their current office location or a meetup spot to a contact by providing latitude, longitude, and a descriptive title.

Properties

Name Meaning
Contact Id The unique identifier of the contact to whom the location will be sent (format: xxx@c.us).
Latitude The latitude coordinate of the location to send.
Longitude The longitude coordinate of the location to send.
Title A descriptive title or name for the location being shared.

Output

The node outputs JSON data representing the response from the CrunchzApp API after attempting to send the location message. This typically includes confirmation details such as message ID, status, timestamps, or error messages if the operation failed.

No binary data output is involved in this operation.

Dependencies

  • Requires an active CrunchzApp API key credential configured in n8n.
  • Depends on network access to https://api.crunchz.app/api to perform the API request.
  • The node uses standard HTTP headers for JSON content negotiation.

Troubleshooting

  • Invalid Contact Id: If the contact ID format is incorrect or the contact does not exist, the API may return an error. Verify the contact ID format and ensure the contact is valid.
  • Incorrect Coordinates: Providing invalid latitude or longitude values may cause the API to reject the request. Ensure coordinates are valid decimal degrees.
  • Authentication Errors: Missing or invalid API credentials will result in authentication failures. Confirm that the API key credential is correctly set up.
  • Network Issues: Connectivity problems to the CrunchzApp API endpoint will prevent message sending. Check internet connection and firewall settings.
  • API Rate Limits: Excessive requests might trigger rate limiting. Review API usage policies if encountering repeated failures.

Links and References

Discussion