CrunchzApp

Overview

This node allows users to delete a specific message by its unique identifier from the CrunchzApp platform. It is useful in scenarios where messages need to be programmatically removed, such as cleaning up outdated notifications, retracting sent information, or managing message lifecycle automatically within workflows.

For example, if you have an automated process that sends messages but later determines some should be deleted based on certain conditions, this node can be used to remove those messages by specifying their IDs.

Properties

The "Message Id" property is required and expects a string representing the unique identifier of the message you want to delete.

Output

The node outputs JSON data reflecting the result of the delete operation. Typically, this will include confirmation of deletion or any error details returned by the API. There is no binary output associated with this operation.

Dependencies

• Requires an active API key credential for CrunchzApp to authenticate requests.
• The node communicates with the CrunchzApp API endpoint at https://api.crunchz.app/api.
• Proper configuration of the API authentication credentials in n8n is necessary.

Troubleshooting

• Invalid Message Id: If the provided message ID does not exist or is malformed, the API may return an error indicating the message could not be found. Verify the ID before attempting deletion.
• Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key is correctly configured and has sufficient permissions.
• Network Issues: Connectivity problems can prevent the node from reaching the CrunchzApp API. Check network settings and retry.
• API Rate Limits: Excessive requests might trigger rate limiting. Implement retries with backoff or reduce request frequency.

Links and References

• CrunchzApp API Documentation (refer to official docs for detailed API behavior)
• n8n Documentation on Creating Custom Nodes and Using Credentials