LeadOS

TIBCON Lead Operations

LeadOS

TIBCON Lead Operations

System Health

Healthy
Environment
—
Last Cron Run
—
Meta Webhooks (24h)
—
Runo Webhooks (24h)
—
Leads Today
—
Total Leads
—
Allocated
—
CAPI Success
—
Pending Alloc
—

Top Callers (Today)

No data yet

Recent Activity

No data yet

Leads

Time Name Phone City Status Caller Alloc CAPI
—

CAPI & Audit Events

Time Type Source Lead CAPI Event Response
—

Webhook Receipts

Received Source Event Type Status Idempotency Key R2 Path
—

Campaigns

Callers

Runo Status → Meta CAPI Mappings

When a caller updates a lead in Runo to one of these statuses, the mapped CAPI event is fired. Click any row to edit.

Runo Status CAPI Event Value Active

Meta Lead Ads

Receives lead webhooks · Sends Conversions API events

checking…
Webhook callback URL
—
Paste this into Meta for Developers → Webhooks → Page object → Callback URL
Verify Token
App Secret
Pixel ID
Access Token
Webhooks last 24h: —
Last received: —
Meta for Developers ↗

To connect Meta Lead Ads:

  1. Set META_APP_SECRET, META_PIXEL_ID, META_ACCESS_TOKEN, and LEADOS_VERIFY_TOKEN in Cloudflare → Workers & Pages → tibcon-lead-os → Settings → Variables and Secrets
  2. Go to Meta for Developers → your app → Webhooks → Page object
  3. Paste the callback URL above and your verify token; click Verify and Save
  4. Subscribe to the leadgen field
  5. Subscribe your TIBCON Facebook Page (the one running ads) under "Add Subscriptions"
  6. Use Meta Ads Manager → your lead ad → Form ID → add to LeadOS as a Campaign

Runo Sheet Sync

Polls the published Google Sheet · matches statuses · fires CAPI

checking…
Sheet CSV URL
—
Set via wrangler.jsonc → vars.RUNO_SHEET_CSV_URL
Sheet URL configured
Sheet events last 24h: —
CAPI fired from sheet last 24h: —
Cursor (last processed timestamp): —
Last sheet event: —

How the sheet sync works:

  1. Runo writes every interaction (call, status change, order) as a row in the Google Sheet.
  2. Hourly cron fetches the published CSV, filters to Meta-sourced rows newer than its last cursor.
  3. Each row is matched to a LeadOS lead by Customer Id (preferred) or phone (last 10 digits).
  4. The lead's status, LeadStatus, Order Value etc. are saved.
  5. If the status maps to a CAPI event in the Status Mappings table, the conversion fires to Meta.
  6. Lead Transfer fires QualifiedLead only when LeadStatus = Qualified / Dealer / Distributor.
  7. Order Closer Status fires Purchase with the actual Order Value.

Admin Users

Change your own password

Currently signed in as —

A full user list is not exposed via the API for security; create new users via the form above.

Payload


  











  

    

      
Lead Detail