Overview

The Krispcall Trigger node listens for webhook events from KrispCall, specifically for new SMS or MMS messages when the 'New SMS_MMS' operation under the 'Webhook' resource is selected. It triggers workflows automatically upon receiving these webhook events, enabling automation based on incoming SMS or MMS messages from KrispCall.

Use Case Examples

1. Automatically process and respond to incoming SMS or MMS messages.
2. Log incoming SMS/MMS data into a CRM system.
3. Trigger notifications or other workflows when a new SMS or MMS is received.

Output

JSON

• bodyData - The JSON data received from the KrispCall webhook event, representing the new SMS or MMS message details.

Dependencies

• Requires KrispCall API credentials for authentication to manage webhooks.

Troubleshooting

• Ensure the KrispCall API credentials are correctly configured and valid to allow webhook creation and deletion.
• Verify that the webhook URL configured in KrispCall matches the path set in the node ('krispcall').
• Check that the webhook is properly created and active in KrispCall to receive events.
• Common errors may include authentication failures or webhook not found errors, which can be resolved by re-authenticating or recreating the webhook.