FlowSmith · sample deliverable

Lead intake, dedupe & routing

This page is generated by the same code that runs the demo — not a mockup. 7 inbound events, including a duplicate submission, a honeypot bot and a malformed email.

3contacts created

2duplicates merged

1rejected + replied

1spam dropped

The duplicate email was normalized (case + whitespace) and matched to the existing contact, so the CRM stays clean and the owner is re-alerted instead of creating a second record.

Event-by-event result

event	name	email	outcome	detail	contact
evt_001	Anna Lee	anna.lee@northstar.io	created	owner alex	1
evt_002	Bob Chen	bob@acme-supply.com	created	owner priya	2
evt_003	Anna Lee	anna.lee@northstar.io	updated	matched contact #1 by email	1
evt_004	Mallory (bot)	winner@prize-claim.xyz	spam	honeypot	-
evt_005	Dana Ruiz	dana.ruiz-at-example.com	rejected	invalid email	-
evt_006	Eve Novak	eve@novak.co	created	owner marco	3
evt_007	Eve Novak	eve@novak.co	updated	matched contact #3 by email	3

Final CRM state

id	name	email	company	owner	budget	touches
#1	Anna Lee	anna.lee@northstar.io	Northstar Studio	alex	core	2
#2	Bob Chen	bob@acme-supply.com	Acme Supply	priya	starter	1
#3	Eve Novak	eve@novak.co	Novak Content	marco	core	2

Run log (what monitoring shows)

[11:11:54] evt=evt_001 created contact #1 owner=alex -> Slack alert + 3-step follow-up scheduled
[11:11:54] evt=evt_002 created contact #2 owner=priya -> Slack alert + 3-step follow-up scheduled
[11:11:54] evt=evt_003 duplicate email -> updated contact #1 (no duplicate created), re-alerted owner
[11:11:54] evt=evt_004 honeypot filled -> dropped silently (no reply to bot)
[11:11:54] evt=evt_005 rejected (invalid email) -> reply asking for a fix
[11:11:54] evt=evt_006 created contact #3 owner=marco -> Slack alert + 3-step follow-up scheduled
[11:11:54] evt=evt_007 duplicate email -> updated contact #3 (no duplicate created), re-alerted owner

← back to FlowSmith