Zoho CRM is the system of record for over 250,000 businesses, according to Zoho’s official product page. If you’re one of them, your lead pipeline probably looks like this: form fills, imported lists, manually entered contacts from trade shows, and whatever your SDRs scrape together from LinkedIn.
What’s missing? The hundreds of website visitors per week who browse your product pages, compare your pricing, and evaluate your solution - then leave without ever entering Zoho.
Leadpipe identifies those visitors - name, email, company, job title, LinkedIn, pages viewed - and sends that data to Zoho CRM automatically. No form fill required. This guide covers the full setup: webhook configuration, Zapier workflow, field mapping, workflow rules, Blueprint automation, and Zoho Analytics reporting.
How the Integration Works
Website Visitor → Leadpipe Identifies → Webhook Fires →
Zapier Routes → Zoho CRM Lead Created → Workflow Rules Execute
Leadpipe’s real-time webhooks fire when a visitor is identified. You route the data to Zoho through Zapier or a direct API connection:
| Path | Setup Time | Best For |
|---|---|---|
| Zapier (Webhook → Zoho CRM) | 15 minutes | Most teams, no-code |
| Zoho Flow (Webhook → Zoho CRM) | 20 minutes | Zoho-native, no extra tools |
| Direct API (Webhook → Zoho API) | 45-60 minutes | Custom logic, high volume |
If you’re already using Zoho Flow (Zoho’s built-in automation platform), you can skip Zapier entirely and route webhooks directly through Flow. This keeps everything inside the Zoho ecosystem.
What You’ll Need
- Leadpipe account - Start free with 500 leads
- Zoho CRM account (Professional plan or higher for workflow rules)
- Zapier account or Zoho Flow (included with Zoho CRM)
- ~20 minutes for setup
Step 1: Set Up the Leadpipe Webhook
- In Leadpipe, go to Settings > Integrations > Webhooks
- Click Add Webhook
- Choose First Match as the trigger type
- Enter your destination URL:
- For Zapier: your Catch Hook URL
- For Zoho Flow: your Flow webhook URL
- Save and send a test event
Use First Match for lead creation. This fires once per identified visitor, creating a clean lead record in Zoho. For ongoing visit tracking, add a second webhook with Every Update later (covered below).
Step 2: Field Mapping - Leadpipe to Zoho CRM
Zoho CRM uses Leads, Contacts, Accounts, and Deals as core modules. Here’s how Leadpipe data maps to each:
Lead Fields
| Leadpipe Field | Zoho CRM Lead Field | Notes |
|---|---|---|
email | Primary identifier | |
first_name | First Name | Standard field |
last_name | Last Name | Standard field |
company_name | Company | Standard field |
job_title | Title | Standard field |
linkedin_url | LinkedIn URL (custom) | Create as custom field |
page_url | First Page Viewed (custom) | Critical for routing |
visit_duration | Visit Duration (custom) | Engagement indicator |
phone | Phone | When available |
city | City | When available |
state | State | When available |
country | Country | When available |
Creating Custom Fields in Zoho CRM
Before connecting, add custom fields:
- Go to Setup > Customization > Modules and Fields > Leads
- Drag “Single Line” field type to add:
- LinkedIn URL (Text)
- First Page Viewed (Text)
- Drag “Number” field type to add:
- Visit Duration (Number, in seconds)
- Set Lead Source picklist values to include “Leadpipe Visitor ID”
These custom fields give your sales team immediate context. When a rep opens a lead and sees “First Page Viewed: /pricing” and “Visit Duration: 247 seconds,” they know exactly how to approach the conversation.
Step 3: Zapier Setup (Step-by-Step)
Trigger
- Create a new Zap
- Trigger: Webhooks by Zapier > Catch Hook
- Copy the webhook URL and add it to Leadpipe
- Send a test event from Leadpipe
Filter
Filter out non-business emails:
email - Exists
AND
email - Does not contain - gmail.com, yahoo.com, hotmail.com, outlook.com
For more filter patterns, see the Zapier automation recipes.
Search for Duplicates
Add a search step before creating the lead:
- Zoho CRM > Find Record (search in Leads module)
- Search by: Email =
{{email}} - Add a Zapier Filter: “Only continue if Zoho CRM Record ID does not exist”
This prevents duplicate leads. If the email already exists in Zoho, the Zap stops.
Create the Lead
Action: Zoho CRM > Create Record (Leads module)
Map all fields from the table above. Additionally set:
- Lead Source: “Leadpipe Visitor ID” (static text)
- Lead Status: “New” or your preferred initial status
- Rating: Based on page viewed (see intent routing below)
Intent-Based Lead Rating
Use Zapier Paths to set different lead ratings based on the page viewed:
Path A: Hot Lead
- Condition:
page_urlcontains “pricing” OR “demo” OR “free-trial” - Lead Rating: “Hot”
Path B: Warm Lead
- Condition:
page_urlcontains “features” OR “product” OR “case-studies” - Lead Rating: “Warm”
Path C: Cold Lead
- Condition: Default
- Lead Rating: “Cold”
This gives your Zoho CRM views and workflows a built-in priority system from day one.
Step 4: Zoho Flow Alternative (No Zapier Needed)
If you prefer keeping everything in the Zoho ecosystem, use Zoho Flow:
Create the Flow
- Go to Zoho Flow > Create Flow
- Trigger: Webhook (Flow provides a URL)
- Add the Flow webhook URL to Leadpipe
- Action: Zoho CRM > Create Record > Leads module
- Map fields same as the Zapier approach
Advantages of Zoho Flow
- No additional subscription (included with Zoho CRM)
- Faster data transfer (stays within Zoho infrastructure)
- Native access to all Zoho CRM features and custom fields
- Built-in error handling and retry logic
Adding Conditional Logic in Flow
Zoho Flow supports IF/ELSE branches:
IF page_url contains "pricing":
→ Create Lead with Rating = "Hot"
→ Assign to SDR team
ELSE IF page_url contains "features":
→ Create Lead with Rating = "Warm"
→ Assign to nurture campaign
ELSE:
→ Create Lead with Rating = "Cold"
→ Add to general pool
Step 5: Zoho CRM Workflow Rules
Once leads are flowing into Zoho, set up workflow rules to automate follow-up:
Workflow 1: Assign Hot Leads to SDR
Trigger: Lead created with Lead Source = “Leadpipe Visitor ID” AND Rating = “Hot” Action:
- Assign to SDR team (round-robin or territory-based)
- Send notification to assigned SDR
- Create task: “Follow up with pricing page visitor within 1 hour”
Workflow 2: Auto-Send Email to Warm Leads
Trigger: Lead created with Lead Source = “Leadpipe Visitor ID” AND Rating = “Warm” Action:
- Send email template: “Thanks for checking us out” (non-salesy, resource-focused)
- Create follow-up task for 48 hours later
- Add to nurture email list
Workflow 3: Territory-Based Routing
Trigger: Lead created with Lead Source = “Leadpipe Visitor ID” Conditions:
- Country = “US” AND State in (“CA”, “OR”, “WA”) → Assign to West Coast rep
- Country = “US” AND State in (“NY”, “MA”, “CT”) → Assign to East Coast rep
- Country = “UK” OR Country = “DE” → Assign to EMEA rep
Workflow 4: Return Visitor Alert
If you set up the Every Update webhook (for return visits), create this workflow:
Trigger: Lead updated with Lead Source = “Leadpipe Visitor ID” AND new note contains “Return visit” Action:
- Send notification to lead owner
- Update lead rating to “Hot” (if not already)
- Create urgent task: “Return visitor - follow up immediately”
Step 6: Blueprint Stages for Identified Visitors
Zoho’s Blueprint feature lets you define a structured sales process. Create a Blueprint specifically for Leadpipe-sourced leads:
Blueprint: Visitor-to-Customer
States (stages):
New → Contacted → Qualified → Demo Scheduled → Proposal → Won/Lost
Transitions:
| From | To | Required Actions |
|---|---|---|
| New → Contacted | Rep sends first outreach (email or LinkedIn) | Mandatory within 4 hours for Hot, 24 hours for Warm |
| Contacted → Qualified | Lead responds positively | Rep updates qualification notes |
| Qualified → Demo Scheduled | Demo date confirmed | Calendar invite sent |
| Demo Scheduled → Proposal | Demo completed | Proposal document attached |
| Proposal → Won | Deal signed | Lead converted to Contact + Deal |
| Proposal → Lost | Deal lost | Loss reason required |
Blueprint SLA Tracking
Zoho Blueprint can enforce time-based SLAs:
- Hot leads: Must be contacted within 4 hours
- Warm leads: Must be contacted within 24 hours
- Cold leads: Must be contacted within 48 hours
Overdue transitions trigger escalation to the team lead. This ensures no identified visitor sits untouched in your CRM.
The speed-to-lead data is clear: faster response times correlate directly with higher conversion rates. Blueprint enforces that speed.
Step 7: Zoho Analytics Reporting
Build dashboards to track the performance of Leadpipe-sourced leads:
Dashboard 1: Visitor-to-Lead Pipeline
| Widget | Chart Type | Data Source |
|---|---|---|
| Leads created (weekly) | Bar chart | Leads filtered by Lead Source |
| Lead rating distribution | Pie chart | Rating field for Leadpipe leads |
| Leads by page viewed | Table | First Page Viewed custom field |
| Average response time | KPI | Blueprint transition timestamps |
Dashboard 2: Conversion Metrics
| Widget | Chart Type | Data Source |
|---|---|---|
| Contacted rate | Funnel | Blueprint stages |
| Qualification rate | Funnel | Blueprint stages |
| Demo booking rate | Funnel | Blueprint stages |
| Win rate vs. form fills | Comparison | Lead Source segmentation |
| Revenue from identified visitors | KPI | Won deals by Lead Source |
Key Metrics to Track
| Metric | How to Measure | Target |
|---|---|---|
| Leads created/week | Filter by Lead Source + date | Depends on traffic |
| Response time | Time from creation to first activity | Under 4 hours (Hot) |
| Qualification rate | Leads reaching “Qualified” stage | 15-25% |
| Demo booking rate | Qualified leads booking demos | 30-50% |
| Win rate (vs. form fills) | Compare by Lead Source | Track over 90 days |
| Revenue attributed | Won deals with Lead Source = Leadpipe | Monthly tracking |
These reports let you prove ROI to your leadership team and optimize your filtering thresholds over time.
Filtering: Only Send ICP Visitors to Zoho
Not every identified visitor should become a Zoho lead. Without filtering, your reps will be drowning in noise - blog readers, competitors, job seekers - and they’ll stop paying attention to the leads that actually matter.
Filter by Job Title
Only create leads for titles that match your buyer personas:
Include titles containing:
VP, Director, Head of, Manager, Chief, Founder, CEO, CTO, CFO, CMO, COO,
President, Owner, Partner
Exclude titles containing:
Intern, Student, Freelance, Blogger, Journalist
Filter by Company Domain
Exclude known non-prospects:
- Competitor domains (add your top 10 competitors)
- Email service domains (gmail.com, yahoo.com, outlook.com)
- Your own company domain
- Known partner/vendor domains (avoid cluttering CRM with existing relationships)
Filter by Page Intent
Not all page visits indicate buying intent. Set minimum thresholds:
| Page Type | Create Lead? | Lead Rating |
|---|---|---|
/pricing, /demo, /contact | Yes | Hot |
/products/*, /features/*, /case-studies | Yes | Warm |
/blog/* (with ICP title) | Yes | Cold |
/blog/* (without ICP title) | No | Skip |
/careers, /about only | No | Skip |
Filter by Visit Duration
Short visits are often accidental or low-intent:
- Under 15 seconds: Skip (bounce)
- 15-60 seconds: Only create if page is high-intent
- Over 60 seconds: Create lead for any ICP-matching visitor
Implement these filters in your Zapier workflow (using Filter steps and Paths) or in Zoho Flow (using IF/ELSE branches).
Advanced: Zoho SalesIQ + Leadpipe
If you’re using Zoho SalesIQ for live chat, combining it with Leadpipe creates a powerful experience:
- Leadpipe identifies a visitor and sends data to Zoho CRM
- Zoho SalesIQ detects the same visitor browsing your site
- SalesIQ shows the rep the visitor’s name, company, and CRM history
- The rep can initiate a chat with full context: “Hi Sarah, I see you’ve been looking at our enterprise plan. Can I answer any questions?”
This turns anonymous chat into personalized, informed conversations. The rep knows the visitor’s name, company, title, and browsing history before the chat even starts.
Return Visitor Tracking with Every Update Webhooks
The First Match webhook creates the lead. But the real sales intelligence comes from tracking return visits over time.
Set up a second Leadpipe webhook with the Every Update trigger, pointing to a separate Zapier workflow or Zoho Flow:
- Webhook fires with updated visitor data (new page_url, visit_duration)
- Search for existing lead in Zoho by email
- If found: Add a note to the lead record: “Return visit - viewed [page_url] for [duration] seconds”
- If high-intent page: Update lead rating to “Hot” and notify lead owner
This gives your reps a complete engagement timeline within the Zoho lead record. When they see a lead who received an email yesterday and just returned to view the pricing page today, that’s a signal to call immediately.
Common Mistakes
Creating leads for every visitor. Not every identified visitor belongs in your pipeline. Filter for ICP fit (job title, company size) before creating Zoho records. See how Pipedrive users handle this for a similar approach.
Ignoring duplicate checking. Always search by email before creating a new lead. Return visitors and existing contacts will create duplicates otherwise.
Not setting Lead Source. Without tagging records, you can’t segment reporting, build workflows, or measure ROI.
Skipping Blueprint. Without a structured follow-up process, leads pile up in “New” status. Blueprint enforces action and tracks SLAs.
No enrichment layer. Leadpipe provides core identity fields. For company revenue, employee count, and technology stack, consider adding Clay enrichment between identification and CRM entry.
What’s Next
With Leadpipe data flowing into Zoho CRM, extend the workflow:
- Add Slack alerts for immediate team notification alongside CRM creation
- Build Zapier automation recipes for multi-step workflows
- Layer Orbit intent data to identify in-market buyers before they visit
- Connect LinkedIn Ads audiences to retarget identified visitors
- Set up an AI SDR to automate first-touch outreach
Try Leadpipe free with 500 leads ->
Start your free trial - 500 leads, no credit card required ->