Leadpipe identifies your website visitors. Zapier puts that data to work. Every time someone is identified on your site, a webhook fires with their name, email, company, job title, pages viewed, and more. Zapier catches that webhook and routes it anywhere: your CRM, Slack, email sequences, spreadsheets, enrichment tools.
These aren’t theoretical workflows. These are 10 specific, ready-to-build Zapier automations that Leadpipe customers are running right now. Each recipe includes the exact trigger, filter, action steps, and expected result so you can set it up in minutes.
Every recipe starts the same way: a Webhooks by Zapier - Catch Hook trigger connected to your Leadpipe webhook. Set that up once, and you can fan out to as many Zaps as you need.
Before You Start: The Universal Trigger
All 10 recipes use the same trigger. Set this up first:
- In Zapier, create a new Zap
- Trigger: Webhooks by Zapier > Catch Hook
- Copy the webhook URL
- In Leadpipe, go to Settings > Integrations > Webhooks
- Add the Zapier URL as a webhook destination
- Select First Match as the trigger type (unless noted otherwise)
- Send a test event
- Zapier captures the payload with all available fields
You’ll reuse this trigger across multiple Zaps. Each recipe below describes only the filter and action steps.
Pro tip: You can point one Leadpipe webhook at one Zapier catch hook, then use Zapier Paths to branch into multiple actions within a single Zap. Or create separate Zaps for each recipe. Separate Zaps are easier to debug; Paths save on your Zapier task count.
Recipe 1: Visitor to HubSpot Contact
Use case: Automatically create HubSpot contacts from identified website visitors. No form fill needed.
Filter:
email - Exists
AND
email - Does not contain - gmail.com, yahoo.com, hotmail.comAction: HubSpot - Create or Update Contact
| Zapier Field | Map To |
|---|---|
{{email}} | |
| First Name | {{first_name}} |
| Last Name | {{last_name}} |
| Company | {{company_name}} |
| Job Title | {{job_title}} |
| Website | {{company_domain}} |
| Lead Source | ”Leadpipe Visitor ID” (static text) |
| LinkedIn URL | {{linkedin_url}} |
Expected result: Every identified business visitor becomes a HubSpot contact within 30 seconds of identification. “Create or Update” prevents duplicates - if the email already exists, HubSpot updates the record instead.
Pairs well with: Leadpipe + Clay + HubSpot Integration Guide for adding enrichment between identification and CRM entry.
Recipe 2: Pricing Page Visitor to Slack Alert
Use case: Instant Slack notification when someone visits your pricing page. Your sales team can respond while the visitor is still browsing.
Filter:
page_url - Contains - /pricing
AND
email - ExistsAction: Slack - Send Channel Message
- Channel: #sales-hot-leads
- Message:
:fire: Pricing Page Visitor Identified
*{{first_name}} {{last_name}}* - {{job_title}}
:office: {{company_name}} ({{company_domain}})
:email: {{email}}
:link: {{linkedin_url}}
:clock: Spent {{visit_duration}} seconds on pricing
:page: Pages viewed: {{pages_viewed}}Expected result: Your #sales-hot-leads channel lights up the moment a pricing page visitor is identified. Reps can claim the lead in-thread and reach out within minutes.
Why pricing page matters: Visitors who reach your pricing page are actively evaluating. Speed-to-lead data shows that responding within one hour yields 7x higher qualification rates. This alert makes sub-hour response the default.
Recipe 3: Visitor to Google Sheets Log
Use case: Keep a running spreadsheet of all identified visitors for analysis, reporting, or sharing with stakeholders who don’t have CRM access.
Filter: None (log all identified visitors)
Action: Google Sheets - Create Spreadsheet Row
| Column | Map To |
|---|---|
| Date | {{timestamp}} |
{{email}} | |
| First Name | {{first_name}} |
| Last Name | {{last_name}} |
| Company | {{company_name}} |
| Domain | {{company_domain}} |
| Job Title | {{job_title}} |
{{linkedin_url}} | |
| Page Viewed | {{page_url}} |
| Duration (sec) | {{visit_duration}} |
| City | {{city}} |
| State | {{state}} |
| Country | {{country}} |
Expected result: A spreadsheet that grows automatically with every identified visitor. No manual data entry. Use it for:
- Weekly reporting to leadership
- Exporting to tools that don’t have direct integrations
- Building custom analyses with pivot tables
- Sharing visitor data with agencies or partners
Pro tip: Add conditional formatting to highlight rows where visit_duration > 120 or page_url contains “/pricing” so high-intent visitors stand out visually.
Recipe 4: High-Intent Visitor to Email Sequence
Use case: Automatically enroll identified visitors in an email sequence when they show high buying intent. No manual list building.
Filter:
page_url - Contains - /pricing OR /demo OR /case-studies
AND
visit_duration - Greater than - 60
AND
email - Does not contain - gmail.com, yahoo.com, hotmail.comAction: Email Tool - Add to Sequence
This works with most email automation platforms. Here’s the mapping for popular tools:
| Platform | Zapier Action | Key Setting |
|---|---|---|
| Instantly | Add Lead to Campaign | Select your warm outreach campaign |
| Apollo | Create Contact + Add to Sequence | Map all fields, select sequence |
| Mailchimp | Add Subscriber to Tag/Audience | Tag as “high-intent-visitor” |
| HubSpot | Add Contact to Workflow | Enroll in nurture sequence |
| Outreach | Create Prospect + Add to Sequence | Map fields, select sequence |
Expected result: High-intent visitors receive a personalized email sequence within minutes of being identified. The sequence should reference their browsing behavior: “I noticed you were checking out our pricing…” feels natural because they literally were.
Important: Only send to visitors showing genuine intent. The filter above ensures you’re targeting people who spent real time on decision-stage pages, not blog readers or accidental clicks.
Recipe 5: Visitor to Salesforce Lead
Use case: Automatically create Salesforce leads from identified visitors with full field mapping and deduplication.
Filter:
email - Exists
AND
company_name - ExistsAction: Salesforce - Find or Create Record
| Salesforce Field | Map To |
|---|---|
| Object | Lead |
| Search Field | |
{{email}} | |
| First Name | {{first_name}} |
| Last Name | {{last_name}} |
| Company | {{company_name}} |
| Title | {{job_title}} |
| Website | {{company_domain}} |
| Lead Source | ”Website Visitor - Leadpipe” |
| City | {{city}} |
| State | {{state}} |
| Country | {{country}} |
Expected result: Every identified business visitor with a company name becomes a Salesforce Lead. The “Find or Create” action prevents duplicates by checking email first.
For the full Salesforce integration guide including workflow rules, assignment logic, and reporting, see Leadpipe + Salesforce: Complete Integration Guide.
Recipe 6: Target Account Visitor to Dedicated Slack Channel
Use case: When a visitor from one of your target accounts hits your site, alert a dedicated channel so your ABM team can coordinate a response.
Filter:
company_domain - Contains - acme.com, bigco.io, targetcorp.com
(list your target account domains)
OR
company_name - Contains - Acme, BigCo, TargetCorp
(backup match on company name)Action: Slack - Send Channel Message
- Channel: #target-accounts (or account-specific channels)
- Message:
:dart: TARGET ACCOUNT VISITOR
*{{first_name}} {{last_name}}* from *{{company_name}}*
:briefcase: {{job_title}}
:email: {{email}}
:link: {{linkedin_url}}
Visited: {{page_url}}
Duration: {{visit_duration}} seconds
Full journey: {{pages_viewed}}
This is a target account. Who's taking this?Expected result: Your ABM team gets immediate visibility when target accounts are on your site. They can coordinate outreach in-thread - the AE checks CRM history, the SDR drafts an email, marketing sends a relevant case study.
Scaling tip: For large target account lists (50+), maintain the domain list in a Google Sheet and use Zapier’s “Lookup Spreadsheet Row” step instead of hardcoding domains in the filter. This lets your ops team update the target list without editing the Zap.
Recipe 7: Visitor to Pipedrive Deal
Use case: Create Pipedrive People and Deals from identified high-intent visitors automatically.
Filter:
page_url - Contains - /pricing OR /demo OR /contact
AND
email - Exists
AND
company_name - ExistsAction 1: Pipedrive - Create Person
| Pipedrive Field | Map To |
|---|---|
| Name | {{first_name}} {{last_name}} |
{{email}} | |
| Organization | {{company_name}} |
| Phone | {{phone}} |
Action 2: Pipedrive - Create Deal
| Pipedrive Field | Map To |
|---|---|
| Title | Leadpipe - {{company_name}} |
| Person | Person ID from Action 1 |
| Pipeline | Your inbound pipeline |
| Stage | First stage |
Expected result: High-intent visitors automatically enter your Pipedrive pipeline as deals with full contact information. For the complete Pipedrive integration guide, see Leadpipe + Pipedrive: Visitor Data to Deals.
Recipe 8: Visitor to Airtable Base
Use case: Build a structured visitor database in Airtable for teams that want maximum flexibility in how they analyze and act on visitor data.
Filter: None (capture all, filter in Airtable views)
Action: Airtable - Create Record
| Airtable Field | Type | Map To |
|---|---|---|
{{email}} | ||
| Name | Single line text | {{first_name}} {{last_name}} |
| Company | Single line text | {{company_name}} |
| Domain | URL | {{company_domain}} |
| Job Title | Single line text | {{job_title}} |
| URL | {{linkedin_url}} | |
| Page Viewed | Single line text | {{page_url}} |
| Duration | Number | {{visit_duration}} |
| Pages Viewed | Long text | {{pages_viewed}} |
| City | Single line text | {{city}} |
| Country | Single line text | {{country}} |
| Date | Date | {{timestamp}} |
| Intent Level | Single select | Use Zapier Formatter to set based on page_url |
| Status | Single select | Default to “New” |
Expected result: A growing Airtable base of identified visitors that you can filter, sort, group, and share. Airtable’s flexibility means you can:
- Create views by intent level (pricing visitors, blog readers)
- Build Kanban boards by status (New, Contacted, Qualified, Won)
- Use Airtable Automations for follow-up triggers
- Share filtered views with sales reps (each rep sees only their territory)
- Connect to Airtable’s AI features for pattern detection
Why Airtable over a CRM? Some teams - especially early-stage companies or marketing teams - don’t need a full CRM. Airtable gives you CRM-like functionality with spreadsheet simplicity. You can always graduate to Salesforce or Pipedrive later and use the Airtable data as your migration source.
Recipe 9: Visitor + Clay Enrichment to CRM
Use case: Identify a visitor with Leadpipe, enrich them with 80+ data points in Clay, then push the complete profile to your CRM. The ultimate data stack.
This is a multi-step Zap that chains three platforms together.
Filter:
email - Exists
AND
email - Does not contain - gmail.com, yahoo.comAction 1: Clay - Add Row to Table
Send the Leadpipe visitor data to a Clay webhook table for enrichment:
| Clay Column | Map To |
|---|---|
{{email}} | |
| First Name | {{first_name}} |
| Last Name | {{last_name}} |
| Company Domain | {{company_domain}} |
| LinkedIn URL | {{linkedin_url}} |
Clay then runs its enrichment waterfall automatically (you configure this in Clay): company revenue, employee count, tech stack, verified work email, phone, seniority level, and more.
Action 2: Wait for Clay enrichment (use Clay’s webhook output or a delay)
Action 3: CRM - Create/Update Contact with enriched data
Push the Clay-enriched data to your CRM of choice with 3-5x more data points than the original Leadpipe payload.
Expected result: Every identified visitor is automatically enriched with firmographic and contact data before entering your CRM. Your reps get a complete profile, not just a name and email.
For the full Clay integration walkthrough, see How to Add Visitor Identification to Clay Waterfall and Leadpipe + Clay + HubSpot Integration Guide.
Recipe 10: Visitor to Personalized Calendar Booking Email
Use case: When a high-intent visitor is identified, automatically send them a personalized email with a calendar booking link. Turn anonymous pricing page visits into booked meetings without manual SDR effort.
Filter:
page_url - Contains - /pricing OR /demo
AND
visit_duration - Greater than - 90
AND
email - Does not contain - gmail.com, yahoo.com, hotmail.com
AND
job_title - ExistsAction 1: Zapier Formatter - Format Text
Create the email body using visitor context:
Hi {{first_name}},
I noticed you were looking at our [pricing/demo] page.
I'd love to walk you through how {{company_name}} could
use [your product] - especially for your team.
Here's my calendar if you'd like to grab 15 minutes:
[YOUR CALENDLY/CAL.COM LINK]
Best,
[Rep Name]Action 2: Gmail/Outlook - Send Email
- To:
{{email}} - From: Your sales rep’s email (or a shared sales alias)
- Subject:
{{first_name}}, quick question about {{company_name}} - Body: Formatted text from Action 1
Expected result: High-intent visitors receive a personal, relevant email within minutes of browsing your pricing page. The email doesn’t feel automated because it references exactly what they were looking at. Include a direct calendar link to remove all friction.
Important caveats:
- Only send to high-intent visitors (pricing/demo page + long duration). Emailing every blog reader will damage your sender reputation.
- Use your real email address, not a marketing alias. This should feel like a 1:1 message.
- Respect opt-outs. Include an unsubscribe mechanism and honor requests immediately.
- Consider routing through your AI SDR for even more personalized messaging based on the visitor’s full page journey.
Choosing the Right Recipes
You don’t need all 10. Start with 2-3 that match your stack and expand from there.
| Your Situation | Start With |
|---|---|
| Using HubSpot | Recipe 1 (HubSpot Contact) + Recipe 2 (Slack Alert) |
| Using Salesforce | Recipe 5 (Salesforce Lead) + Recipe 2 (Slack Alert) |
| Using Pipedrive | Recipe 7 (Pipedrive Deal) + Recipe 2 (Slack Alert) |
| No CRM yet | Recipe 3 (Google Sheets) + Recipe 8 (Airtable) |
| ABM team | Recipe 6 (Target Account Slack) + Recipe 9 (Clay Enrichment) |
| Solo founder / small team | Recipe 2 (Slack Alert) + Recipe 10 (Calendar Email) |
| Data-first approach | Recipe 9 (Clay Enrichment) + Recipe 3 (Google Sheets) |
Zapier Plan Considerations
Each Zap uses one or more tasks per execution. Here’s the task math:
| Recipe | Tasks per Visitor |
|---|---|
| Single action (Sheets, Slack) | 1-2 tasks |
| Filter + action (HubSpot, Salesforce) | 2-3 tasks |
| Multi-step (Clay + CRM, Calendar email) | 3-5 tasks |
With 500 identified visitors per month and 3 Zaps averaging 2 tasks each, you’ll use roughly 3,000 tasks/month. Zapier’s Starter plan (750 tasks) won’t cut it. Their Professional plan (2,000 tasks) or Team plan (unlimited) is more realistic for active Leadpipe integrations.
Debugging Your Zaps
When things don’t work:
Webhook not firing: Check Leadpipe’s webhook logs under Settings > Integrations. Look for delivery status and error codes. The most common issue is an incorrect URL.
Filter blocking everything: Temporarily remove the filter and check if the action works. Then add filter conditions back one at a time to find the culprit.
Duplicate records: Make sure you’re using “Find or Create” (not just “Create”) for CRM actions. Also confirm your Leadpipe webhook is set to First Match, not Every Update.
Missing fields: Some Leadpipe fields may be null for certain visitors (phone is available ~40-60% of the time). Use Zapier’s “Only continue if exists” filter to handle missing data gracefully.
Slow delivery: Zapier polls every 1-15 minutes on lower plans. For true real-time delivery, upgrade to a plan with Instant triggers or use Leadpipe’s webhooks with a direct API integration. If you prefer a self-hosted, open-source alternative to Zapier, check out our Leadpipe + n8n automation guide.
What’s Next
Try Leadpipe free with 500 leads -> and start building these automations. You’ll have identified visitors flowing into your tools within the hour.
Once you’re up and running, explore these deeper integration guides:
- Build a complete AI SDR pipeline from visitor to booked meeting
- Feed visitor data into your AI agent for autonomous outreach
- Add Leadpipe to your Clay waterfall for maximum enrichment coverage
Related Articles
- Webhook Payload Reference: Every Visitor Data Field
- Leadpipe + Salesforce: Complete Integration Guide
- Leadpipe + Pipedrive: Visitor Data to Deals
- How to Add Visitor Identification to Clay Waterfall
- Visitor ID + Slack: Real-Time Lead Alerts That Work
- Build a Custom AI SDR with Leadpipe and OpenAI
- Leadpipe + Clay + HubSpot Integration Guide
- Leadpipe + n8n Automation Recipes
