Overview

The Krispcall Trigger node listens for webhook events from KrispCall, specifically triggering workflows based on events such as receiving a new voicemail. It is useful for automating actions in response to KrispCall events, like processing voicemails or other webhook notifications.

Use Case Examples

1. Automatically save new voicemails to a cloud storage service when a voicemail is received.
2. Trigger a notification or alert in a team chat when a new voicemail arrives via KrispCall.

Output

JSON

• bodyData - The JSON data received from the KrispCall webhook event, such as details of the new voicemail.

Dependencies

• Requires KrispCall API credentials for authentication to manage and receive webhook events.

Troubleshooting

• If the webhook does not trigger, ensure the webhook URL is correctly set up in KrispCall and the node has valid API credentials.
• Common errors may include missing or invalid webhook ID when attempting to delete or manage webhooks; ensure the webhook is properly created before deletion attempts.
• Check that the incoming webhook payload matches expected structure to avoid processing errors.