Actions22
- Channel Actions
- Chat Actions
- Message Actions
- Contact Actions
- OTP Code Actions
- OTP Link Actions
Overview
This node allows sending text messages to a specified contact via the CrunchzApp API. It is useful in scenarios where automated messaging is needed, such as customer support notifications, marketing campaigns, or alert systems. For example, you can use this node to send a confirmation message to a user after they complete a form or to notify a team member about an important event.
Properties
| Name | Meaning |
|---|---|
| Contact Id | The unique identifier of the contact to whom the message will be sent (format: xxx@c.us). |
| Message | The text content of the message to send. |
Output
The node outputs JSON data representing the response from the CrunchzApp API after attempting to send the message. This typically includes information about the success or failure of the message delivery. The node does not output binary data.
Dependencies
- Requires an active CrunchzApp API key credential configured in n8n.
- Depends on the CrunchzApp API endpoint at
https://api.crunchz.app/api. - 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). - Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up in n8n.
- Message Delivery Failures: Network issues or API downtime can prevent message sending. Check connectivity and CrunchzApp service status.
- Empty Message: Sending an empty message string might result in an error or no action. Always provide a non-empty message.
Links and References
- CrunchzApp API Documentation (assumed URL based on baseURL)
- n8n documentation on Using Credentials
- General info on Sending Messages with APIs