← Back to Work
Automation + Integration[PIPELINE][CLIENT WORK][REAL BUILD SHOWN]
Lead Qualification & CRM Routing
Form leads deduplicated, scored, and routed into DripJobsA Zapier workflow that takes each new Typeform lead, checks it against existing records, scores it in a code step, and creates it in DripJobs, so every submission follows the same path into the job system.
- My role
- Designed and built the Zap end to end: the Typeform trigger, the Zapier Tables duplicate check and filter, the Code by Zapier scoring step, and the field mapping into DripJobs.
- Built with
- Zapier, Typeform, Code by Zapier, Zapier Tables, DripJobs
- Status
- Client work, published in Zapier
- 5-step Zapfrom form entry to CRM lead, in one published workflow
- Duplicate gatea repeat submission stops before it reaches DripJobs
- Code-based scoringevery new lead scored before it's created
Before
The problem
Incoming form leads needed a consistent path into DripJobs. Without one, a repeat submission could become a second record, and every lead arrived the same way, whatever it looked like.
The system
How the pieces connect
- TypeformNew entry
- Zapier TablesFind existing records
- Filter by ZapierSkip duplicates
- Code by ZapierScore the lead
- DripJobsCreate the lead
Proof
The real build
Real buildZapier workflow
Step by step
How it works
- 1A new Typeform entry starts the Zap. No one copies the submission anywhere.
- 2Zapier Tables is searched for an existing record that matches the lead.
- 3A filter ends the run when a match is found, so a repeat submission never becomes a second DripJobs lead.
- 4A Code by Zapier step scores the lead before it goes any further.
- 5The lead is created in DripJobs, with its name, email, phone, and lead source mapped across.
After
What changed
› New form leads reach DripJobs through one consistent, automated path instead of being entered by hand.
› Repeat submissions stop at the duplicate gate instead of becoming second records.
› Every new lead is scored by the same logic before it's created.
› No time-saved, lead-volume, or conversion figures are claimed here; the workflow is the proof.
Stack
AlsoFilter by Zapier
For technical readers
Technical detail
The problem, in detail
Leads came in through a Typeform and needed to end up as leads in DripJobs, the job system the team works from.
› Moving each submission across by hand was repeated manual work for every new lead.
› Nothing stopped someone who submitted the form twice from becoming two records.
› Every submission arrived the same way, with nothing to tell one lead from another.
Build notes
A five-step Zap in Zapier, designed and built end to end: trigger, duplicate check, scoring, and destination mapping.
› Trigger: a Typeform New Entry step starts a run for each submission.
› Lookup: a Zapier Tables Find Records step searches existing records for the incoming lead.
› Duplicate gate: a Filter by Zapier step, Skip Duplicates, ends the run when the lookup finds a match, before anything is written downstream.
› Scoring: a Code by Zapier step, Score Lead, applies the scoring logic in code, so every new lead is judged by the same rules.
› Destination: a DripJobs Create Lead step maps the lead's name, email, phone, and lead source into a new DripJobs lead.
Pipeline breakdown
01
Typeform: New Entrytrigger, one run per form submission
02
Zapier Tables: Find Recordslooks up existing records for the incoming lead
03
Filter by Zapier: Skip Duplicatesends the run when the lookup returns a match
04
Code by Zapier: Score Leadscoring logic in code, run on every lead that passes the filter
05
DripJobs: Create Leadmaps name, email, phone, and lead source into a new lead