Every lead, routed.
Sign in with your Sorbet workspace account to manage lead flows, review the audit log, and connect Meta or Google accounts.
Sign in →Flows.
Each flow carries one source into one destination. Leads arrive on a secret webhook URL, get mapped, and land in Brevo or the Sorbet DB.
Clients
who you collect leads forLive flows
source → destinationNew flow
from → to → field mapLeads.
Every inbound lead, and whether it reached its destination. A received row that never moved on usually means the field map didn't match the form.
Contacts.
Leads stored natively. Only flows with target Sorbet DB land here — including leads with no email, which are deduped on their phone instead (and never merged when they give neither).
Wiring each source.
How to point each kind of form at a flow's webhook.
Website (direct API)
For a custom site or app: create a flow with source Website and have your
backend or frontend POST the lead as JSON to the flow's webhook URL. The
field map keys are the JSON keys you send. The endpoint always returns 200
once the lead is logged; only an unknown token returns 404.
fetch("https://…/webhook/<token>", {
method:"POST", headers:{"content-type":"application/json"},
body: JSON.stringify({ email:"[email protected]", name:"Jane", phone:"+972…" })
})
WordPress
Create a flow with source WordPress and a field map keyed by your form's field names. In the form plugin (Elementor Pro / WPForms / Gravity / Fluent) add a Webhook action pointing at the flow's webhook URL.
Wix
Create a flow with source Wix and a field map keyed by your Wix form field names. In Wix → Automations → trigger "Form submitted" → action "Send via Webhook" (POST JSON) pointing at the flow's webhook URL.
Destination
Each flow delivers to either Brevo (needs an API key + list) or the native Sorbet DB (no external account — leads are deduped by email and shown under Contacts).
Connect an account (Meta / Google) — the easy way
For server-side tracking attribution: create a flow with source Traffic (target locks to the Traffic log). In the SST (sGTM) container add an HTTP-request tag that POSTs the event — utm_source, utm_medium, utm_campaign, gclid, page, referrer — to the flow's Traffic URL. Events show in the CRM's Traffic view; nothing is delivered to Brevo or the contact book.
In the flow form pick source Meta Lead Ads or Google Ads, click
Connect account, and sign the client in to the Sorbet-Hooks app. You're sent back
here with their Pages / Ads accounts in a dropdown — pick one, choose the destination and
field map, and hit Create flow. For Meta we auto-subscribe the chosen Page to
leadgen; for Google we record the account and hand you the webhook URL + key
to drop into the Lead Form asset. (The Google account list needs the Ads API Developer
Token; without it you can still type the customer id by hand.)
Google Ads (manual)
Create a flow with source Google Ads and a field map keyed by Google column IDs
(EMAIL, FULL_NAME, PHONE_NUMBER, …). In Google Ads
→ the Lead Form asset → Webhook integration, paste the flow's Google webhook URL as the
URL and its key as the Key, then click "Send test data".
Meta Lead Ads (manual)
Prefer Connect account above. To wire by hand: all Pages share one app-level
callback, . In the Meta app (Sorbet-Hooks) → Webhooks → Page,
set the Callback URL to that, the Verify Token to the server's
META_VERIFY_TOKEN, subscribe to the leadgen field, then
subscribe each client Page to the app. Create a flow per Page with its
meta_page_id + long-lived meta_page_token; field map keys are
the Meta form field names (email, full_name,
phone_number, …).
