Webhooks & Callbacks

A webhook is how CallMangal tells your own systems what happened on a call, without you needing to poll for it. When a call ends, CallMangal can send the result to a URL you control.

The general flow

Call completed
      ↓
Call outcome and any extracted information
      ↓
Webhook callback to your configured URL
      ↓
Your CRM, workflow tool, or backend acts on it

This is the same information a human would see reviewing the call in CallMangal — outcome, and whatever the workflow was built to capture — delivered automatically to whatever system needs to act next.

Payload shape not published here

The exact structure of a webhook payload is part of CallMangal's API and depends on your integration setup. This page describes the flow conceptually; it does not publish an example payload, since doing so without generating it from CallMangal's actual implementation would risk documenting something that does not match what you receive. Confirm the current payload shape with the CallMangal team when you configure a webhook.

What a webhook is useful for

• Updating a CRM — pushing a new lead, a qualification result, or a call outcome into HubSpot, Salesforce, Zoho, or another connected CRM.
• Triggering a workflow tool — Zapier, Make, or a similar automation platform, which can then fan out to other systems.
• Notifying your own backend — if you have internal tooling that should react to a call the moment it ends.
• Keeping a spreadsheet or internal record current — for simpler setups that do not need a full CRM.

REST API

Alongside webhooks (CallMangal pushing data to you), CallMangal also supports REST API access for triggering actions and reading data. Full endpoint documentation is not yet published; ask the CallMangal team about current API access for your account.

Next

• Telephony Overview
• MCP Overview