CrunchzApp icon

CrunchzApp

Interact with CrunchzApp API

Actions22

Overview

This node allows sending a video message to a specified contact via the CrunchzApp API. It is useful in scenarios where you want to automate multimedia communication, such as sending promotional videos, tutorials, or personalized video messages to users or customers. For example, a marketing automation workflow could use this node to send product demo videos to leads, or a customer support process might send instructional videos to help resolve issues.

Properties

Name Meaning
Contact Id The unique identifier of the contact to whom the video will be sent (format: xxx@c.us).
Video Url The URL pointing to the video file to be sent (e.g., an MP4 file hosted online).
Caption An optional text caption that accompanies the video message.

Output

The node outputs JSON data representing the response from the CrunchzApp API after attempting to send the video message. This typically includes information about the success or failure of the operation and any metadata related to the sent message. The node does not output binary data.

Dependencies

  • Requires an active CrunchzApp API key credential configured in n8n.
  • Depends on internet access to reach the CrunchzApp API endpoint at https://api.crunchz.app/api.
  • The video must be accessible via a publicly reachable URL.

Troubleshooting

  • Invalid Contact Id: If the contact ID is malformed or does not exist, the API may return an error indicating the contact was not found. Verify the contact ID format and existence.
  • Video URL Issues: If the video URL is inaccessible, invalid, or points to an unsupported format, the message sending will fail. Ensure the URL is correct and the video is in a supported format like MP4.
  • Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Confirm that the CrunchzApp API key is correctly set up in n8n credentials.
  • API Rate Limits or Downtime: If the API service is down or rate limits are exceeded, requests may fail. Check CrunchzApp service status and consider retry logic.

Links and References

Discussion