ManualAutomatic
Two sources normalized04 · Website leads + Meta Lead Ads
Website & Meta Ads Lead Extraction
Switch between two real lead sources and watch each payload become one standardized, qualified and correctly attributed CRM opportunity.
Interactive simulation using hard-coded sample leads. The n8n, WAPI, Retell AI, CRM and database panels demonstrate production logic; no real client data is transmitted.
Automation runningLead-source extraction simulationSample 1 of 2 · WEB-7314
Live workflow funnelSource payload captured
Waiting for the trigger…
0%AL
Amelia Lewis+44 •••• ••• 164 · Website form
New enquiryWaiting for the automation trigger
The approved conversation will appear here as the funnel runs.
Automation activityOne visible audit trail
Simulation time- 00:001Source-specific payload received with attributionThe website webhook or Meta Lead Ads webhook receives the original lead data.
- 00:022Required-field and permission checks passedRequired contact fields, consent evidence and source identifiers are validated.
- 00:043n8n mapping complete · no duplicate foundn8n maps two different payload formats into one clean lead schema and checks for duplicates.
- 00:084First response started through the approved channelWAPI or Retell AI starts the correct approved conversation for the lead source and intent.
- 00:445Qualified lead assigned to the right property adviserBudget, timing and property interest determine the correct team and next action.
- 00:526CRM, database, attribution and agent alert syncedThe lead, conversation, campaign source, owner and appointment are written into one record.
Often lostPreserved
Source through bookingHiddenChecked
Before agent routingInconsistentUnder 1 min
Illustrative workflowThis demo illustrates workflow behaviour. Actual results depend on lead quality, volume, tools, team adoption and market conditions.
Background engine · source extraction
Two lead sources. Two payloads. One clean operating workflow.
Simulated backend
Website forms and Meta Lead Ads arrive differently. The automation preserves each source’s useful context, converts both into a standard lead record, starts the right response and keeps campaign attribution visible through the handoff.
TriggerWebsite form submission or Meta Lead Ads webhookWEB-7314 · Website form
Form + page context
Payload received
Map, check and route
WAPI / Retell AI
One clean record
Human next action
Source payloadWebsite webhook
JSON- submission_id
- waiting…
- page
- waiting…
- utm_source
- waiting…
- interest
- waiting…
- consent
- waiting…
n8n execution logPropertyFlow / WEB-7314
Running- 01·
Waiting for previous node…
- 02·
Waiting for previous node…
- 03·
Waiting for previous node…
- 04·
Waiting for previous node…
- 05·
Waiting for previous node…
- 06·
Waiting for previous node…
Real-world fit
Built around the moments where property opportunities usually leak.
The final system is configured around your lead sources, approved conversation logic, CRM stages, calendars, routing rules and human escalation points.
01Property and project website forms
02Meta Lead Ads campaigns
03Seller valuation forms
04Open-house registrations
05Campaign-to-appointment attribution
06Multi-source lead deduplication
Explore another workflow
From simulation to your workflow
Want this system built around your real lead process?
MyDesignNexus can connect your approved lead sources, AI calling or messaging, website, CRM, calendars and custom software into one measurable operating flow.