Use case

Process inbound leads automatically.

Form submission arrives → AI scores and enriches the lead → hot leads routed for human review → warm leads get an automated follow-up → everything logged to your CRM.

Start building — freeRead the docs
The problem

Hot leads go cold while someone decides what to do with them.

Form submissions pile up. Someone manually reviews each one, decides if it's worth pursuing, finds the right person to handle it, sends a reply. The hot leads are 48 hours old by the time they get a response.

The fix isn't a CRM plugin. It's a workflow that processes every lead the moment it arrives and routes it to exactly the right place.

The workflow

Every lead processed in under 30 seconds.

lead-processing.mdtrigger: webhook
# Inbound Lead Processing
 
### 1. Receive form submission
Accept the webhook payload with name, email, company, and message.
 
### 2. Enrich lead data
Look up the company domain for size, industry, and funding stage using the enrichment API.
 
### 3. AI scoring
Score the lead as hot, warm, or cold based on company size, intent signals, and message content. Depends on step 2.
 
### 4. Route by score
Hot leads go to step 5 (human review). Warm leads go to step 6 (auto-nurture). Cold leads go to step 7 (log only).
 
### 5. Sales team alert (hot only)
Post to #hot-leads Slack channel with full context. Wait for a sales rep to claim within 2 hours.
 
### 6. Log to CRM
Create a contact in the CRM with score, enrichment data, and assigned rep (if claimed).
Why CFFBRW

AI scoring, human gates, and self-healing — in one workflow.

AI
Lead scoring without a model to train
The ai_call step reads the lead data and enrichment result, applies your criteria in plain English, and returns hot/warm/cold. No ML pipeline, no training data.
⏸
Hot leads wait for a human — not a timer
The human_approval step pauses the workflow until a sales rep responds. Not a 5-minute timeout — a real gate with a configurable TTL.
🔁
CRM API changes? It heals.
If the CRM API returns an unexpected error, AI recovery diagnoses and retries before escalating. Your pipeline keeps running.
Step types used

Built with 5 step types and a webhook trigger.

webhook trigger — fires on every form submission
http_request — enriches company data
ai_call — scores lead as hot/warm/cold
conditional — routes by score
human_approval — waits for sales rep claim
connector — logs to CRM + Slack
Get started

Every lead processed
the moment it arrives.

Write the workflow in plain English. CFFBRW compiles and deploys it. No credit card. No config files.

Start building — freeSee more examples