CrunchzApp icon

CrunchzApp

Interact with CrunchzApp API

Actions22

Overview

This node allows sending a location message to a specified contact via the CrunchzApp API. It is useful in scenarios where you want to share geographic coordinates with a contact, such as providing directions, sharing meeting points, or indicating places of interest.

For example, a user can send their office location or a meetup spot directly to a contact's chat by specifying 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 (e.g., "Our office").

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 about the message delivery status or any error information 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 the CrunchzApp API endpoint at https://api.crunchz.app/api.
  • The node uses standard HTTP headers for JSON communication (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Invalid Contact Id: If the contact ID format is incorrect or the contact does not exist, the API may return an error. Ensure the contact ID follows the expected pattern (e.g., xxx@c.us).
  • Incorrect Coordinates: Providing invalid latitude or longitude values might cause the API to reject the request. Verify that latitude is between -90 and 90, and longitude is between -180 and 180.
  • Authentication Errors: Missing or invalid API credentials will prevent the node from successfully sending messages. Confirm that the CrunchzApp API key is correctly set up in n8n credentials.
  • Network Issues: Connectivity problems or API downtime can cause request failures. Check network access and CrunchzApp service status.
  • Error Messages: The node will relay error messages returned by the CrunchzApp API. Review these messages for specific issues like quota limits, malformed requests, or permission errors.

Links and References

Discussion