CallerDesk WebhookInstall

Summary

Trigger workflow execution upon receiving a CallerDesk webhook HTTP request with configurable authentication and filtering options.

Inputs

• HTTP Method — Choose the HTTP method (GET or POST) the webhook listens to.
• Account ID (required) — Specify the CallerDesk account ID to filter incoming webhooks; only calls matching this ID trigger the workflow.
• Path (required) — Set the webhook's URL path suffix after the Account ID.
• Authentication — Select the authentication type (None, Basic, Header, or JWT) for securing the webhook.
• Respond — Determine when the webhook responds: immediately on receipt, after the last node finishes, via a Respond to Webhook node, or streaming.
• Trigger Only If Status — Filter which call status events trigger the workflow (All, Answered, Missed, Failed).
• Require Source Number — Require the presence of a source number in the webhook data to trigger.
• Normalize Output — Normalize the webhook output to a consistent structured format with enriched call details.

Output shape

a single JSON object representing the incoming call data with optional normalization

Returns an empty workflow data array if the webhook data does not match the specified Account ID, status filter, or required source number. When normalization is enabled, the output includes fields like sourceNumber, destinationNumber, status, call durations, start/end times in ISO format, callSid, recording URL, and the raw webhook data. Response to the webhook request depends on the 'Respond' setting, with the default providing an immediate success message.

Links

• n8n community nodes installation guide