Overview

The Krispcall Trigger node activates workflows based on webhook events from KrispCall, specifically for the 'New SMS/MMS Sent' operation under the 'Webhook' resource. It listens for incoming POST requests from KrispCall when a new SMS or MMS message is sent, allowing automation workflows to process these events automatically. This is useful for scenarios such as logging messages, triggering notifications, or integrating SMS/MMS data with other systems.

Use Case Examples

1. Automatically log every new SMS/MMS sent via KrispCall into a CRM system.
2. Trigger an alert or notification in a team chat when a new SMS/MMS is sent.
3. Process and analyze SMS/MMS content for sentiment or keyword detection in real-time.

Output

JSON

• bodyData - The JSON payload received from the KrispCall webhook representing the new SMS/MMS sent event

Dependencies

• Requires KrispCall API credentials for authentication to manage webhooks.

Troubleshooting

• Ensure the KrispCall API credentials are correctly configured and valid to create and delete webhooks.
• Verify that the webhook URL configured in KrispCall matches the path 'krispcall' used by the node to receive events.
• Check that the incoming webhook payload matches the expected format; otherwise, the workflow may not process the data correctly.

Links

• KrispCall Webhook API Documentation - Official documentation for setting up and managing KrispCall webhooks.