Terminal
Terminal/Skill
Walks you through building a Clay workflow that routes inbound leads from a form or webhook to a rep, sequence or CRM.
By Clay
Works with
npx skills add clay-run/agent-plugins --skill workflows-inbound-lead-routingGuide customers through building an inbound lead routing workflow in Clay Workflows. Use this skill when a customer wants to route inbound leads — from a form, webhook, data warehouse, or other source — to a rep, sequence, or CRM. Be opinionated and directive. Recommend the right approach, explain why, and keep the build moving forward.
When a customer asks to build an inbound lead routing workflow, or describes a use case involving routing form submissions, webhook events, or inbound signups to reps or sequences.
Start by telling the customer:
"For inbound lead routing, we'll use a webhook as the trigger. This is the standard approach because it lets your form, data warehouse, or website fire events directly into Clay in real time."
Available triggers (present as alternatives only if the customer pushes back or has a specific constraint):
Ask the customer:
"Are you capturing leads through an inbound form, like Typeform, or is this coming from another source like your data warehouse or website?"
Before building, gather all five answers across at least two messages. Ask no more than three questions per message. Do not build until you have the answers.
Q1 — CRM
"Which CRM are you using?"
Q2 — Scoring Model
"Do you have an existing lead scoring model, or do we need to build one?"
Q3 — Rep Routing
"When a tier 1 lead comes in, how do you want the rep to be notified?"
Options (pick one):
Q4 — Sequencer
"Are you using an external sequencer like Outreach or Salesloft, or Clay's native sequencer?"
Q5 — Disqualification Handling
Ask as two separate yes/no questions:
If both answers are no, end without further action.
Keep enrichment and scoring steps sequential. Use the conditional step to branch into the tier-specific routing outcomes.
The standard happy path:
Webhook Trigger
→ Run Enrichment (firmographic + contact data)
→ Run Code (scoring model)
→ Conditional Logic (tier routing)
→ Route (rep notification / sequence / disqualify)
Walk the customer through each node:
"First, we'll enrich the inbound lead to fill in any missing data — company size, industry, job title, and any intent signals. This gives the scoring model everything it needs."
Ask: "Do you want to enrich at the person level, company level, or both?"
"Next, we'll run a scoring model to tier the lead. This code node will take the enriched data and output a score or tier (e.g., Tier 1 / Tier 2 / Disqualified)."
If building from scratch:
"Tell me what matters most for a high-quality lead — company size, industry, job title, intent signals? I'll help you translate that into a scoring formula."
Typical inputs to the scoring model:
"Now we'll add conditional logic to route based on the score. What are your tiers?"
Standard structure:
Additional conditional branches to offer if relevant:
Build the routing outcome based on answers from Step 2:
If routing to a rep:
If adding to a sequence:
If disqualifying:
Once all questions are answered and the node structure is clear, summarize the workflow back to the customer before building:
"Here's the workflow we're going to build:
- [Selected trigger] trigger from [source]
- Enrich at [person/company/both] level
- Score the lead using [existing model / model we'll build] based on [inputs]
- Route Tier 1 leads to [rep via Slack/CRM task/email], Tier 2 to [sequence], and disqualified leads to [dead end/nurture/CRM tag]
Does that look right?"
Only proceed to build once the customer confirms.
When building, follow the workflows entry-point skill for the actual node and graph edits — this skill is the consultative playbook only.