Sales teams live in Salesforce. If your AI voice agent cannot write outcomes back to leads, contacts, and tasks, reps will ignore the channel. VOXBRIDGE webhooks close that gap by pushing structured call events to any HTTPS endpoint you control—including Salesforce via Flow, Apex, or middleware like Zapier and Workato. This guide walks through a pragmatic integration you can stand up in a single working session.
What VOXBRIDGE sends on each call
After a conversation ends or reaches a milestone, VOXBRIDGE emits JSON webhooks you configure in the dashboard at voxbridge.cc. Typical payloads include call identifiers, direction (inbound or outbound), E.164 phone numbers, duration, disposition, transcript summary, captured entities (name, email, preferred time), and recording URLs when enabled.
Design your Salesforce mapping around objects you already use:
- Lead or Contact — match on phone number with normalization rules for country codes.
- Task or Call — store duration, disposition, and a link to the recording for coaching.
- Custom fields — AI intent, sentiment, or appointment slot chosen during the call.
Consult the event catalog in our docs before you hard-code field names; versioning is documented there so you can pin to stable schemas in sandbox first.
Choose your integration pattern
Three patterns cover most revenue teams. Pick based on who owns Salesforce admin versus engineering time.
Salesforce Flow + Named Credential. Best when admins can publish without a release cycle. Create an autolaunched Flow triggered by an inbound Platform Event or external service. Store your webhook signing secret in a Named Credential. Flow parses JSON with invocable actions or a small Apex invocable if parsing is complex.
Apex REST endpoint. Best when you need tight validation, idempotency keys, and bulk-safe triggers. Expose a REST resource that verifies HMAC signatures from VOXBRIDGE, enqueues work asynchronously, and upserts records in a single transaction boundary.
Middleware. Fastest for prototypes. Point the webhook to Zapier or Make, map fields visually, and write to Salesforce with OAuth. Trade-off: per-task cost and less control over retry semantics.
Always verify webhook signatures in production. Unsigned test endpoints are fine in sandbox; never ship them to a public URL.
Ten-minute path with Flow and a secure endpoint
In VOXBRIDGE, open Integrations and add a webhook URL pointing to your Salesforce Experience Cloud site, Heroku app, or API gateway—anything that terminates TLS and returns 2xx quickly. Subscribe to call.completed and call.transferred to start; add granular events later.
In Salesforce Setup, create a Named Credential for your verifier service if Flow cannot validate HMAC directly. Many teams deploy a fifteen-line Cloudflare Worker or AWS Lambda that validates the signature, then calls a Flow invocable URL with a shared secret. That keeps secrets out of Flow screens and preserves auditability.
Map payload fields to a Platform Event named Voice_Call_Completed__e. A record-triggered Flow on that event finds Lead by mobile phone using a formula that strips non-digits. On match, create a Task with subject “AI call — {disposition}”, paste summary into description, and set Activity Date to today. On no match, create a Lead with source “VOXBRIDGE Voice” and assign per your round-robin rules.
Idempotency, retries, and duplicate leads
Webhooks retry on timeouts and 5xx responses. Store the VOXBRIDGE call ID in a custom field with a unique external ID constraint so a retry does not create duplicate tasks. Respond 200 as soon as you enqueue work; perform heavy transcript processing asynchronously.
Phone matching is messy. Maintain a normalization Apex utility that converts numbers to E.164 using the org’s default locale, and log near-miss matches for data stewards. If marketing uses multiple numbers per account, consider matching on Contact Id passed through outbound API variables instead of caller ID alone.
Test in sandbox, then promote
Use Salesforce sandbox with a VOXBRIDGE test project and a single verified number. Place three calls: happy path completion, transfer to human, and abandoned call. Confirm Tasks, field updates, and reporting dashboards. Enable debug logs briefly to capture Flow faults, then disable to avoid noise.
When promoting to production, rotate webhook secrets, update Named Credentials, and re-run a smoke test from a known mobile. Document the runbook for rev ops: which dispositions mean “sales qualified” versus “support only”.
Measure impact inside Salesforce
Build a report type joining Tasks created by voice to Opportunities. Track stage movement within seven days of AI contact. Compare to a cohort without voice touch for the same lead source. Pair with pricing assumptions so leadership sees cost per qualified conversation, not just technical success.
If you are evaluating platforms, see how webhook depth and telephony controls compare on our compare page. When you are ready to wire production, create your project at signup and paste your Salesforce endpoint into the webhook panel—most teams ship the first useful sync the same day they finish sandbox testing.