.svg)
Overview
Salesloft and ZoomInfo are two of the most widely deployed tools in the B2B GTM stack, but for most teams they operate as separate islands. Salesloft handles cadence execution and engagement tracking. ZoomInfo provides intent data, contact enrichment, and firmographic intelligence. The integration between them has existed for years, but the 2025 partnership expansion turned what was a basic contact push into something approaching a real-time signal-to-engagement pipeline.
This matters because the gap between "knowing an account is in-market" and "reaching the right person with the right message" is where most outbound programs lose. A ZoomInfo intent spike means nothing if it takes your team two days to identify contacts, research the account, and build a cadence. The Salesloft + ZoomInfo integration, when configured properly, can compress that cycle from days to minutes.
This guide covers the practical mechanics of making the integration work: how intent signals flow into Salesloft, how contact enrichment feeds cadence personalization, and where the setup still falls short. If you're running both tools and haven't configured the integration beyond the default settings, you're leaving significant pipeline on the table.
What the Salesloft + ZoomInfo Partnership Actually Includes
The expanded partnership between Salesloft and ZoomInfo goes beyond the original "export contacts to cadence" workflow. Here's what the integration covers in its current form:
Intent Signal Passthrough
ZoomInfo's intent data, powered by Bombora's cooperative data network, can now trigger automated workflows in Salesloft. When an account surges on topics relevant to your product, that signal can automatically create or update records in Salesloft and initiate cadence enrollment. This is the highest-value piece of the integration, and the one most teams under-configure.
Contact Enrichment at the Point of Engagement
Rather than enriching contacts in bulk and hoping the data stays fresh, the integration supports on-demand enrichment. When a contact enters a Salesloft cadence, ZoomInfo data, including direct dials, verified emails, title, department, and firmographic context, can be pulled in real time. This matters because ZoomInfo's data decays fast. A phone number that was accurate three months ago during a bulk export may be dead today.
Buying Committee Mapping
ZoomInfo's org chart and reporting structure data can feed into Salesloft's account-level views. For teams running buying committee plays, this means you can identify and enroll not just the primary contact but the full decision-making group, including the economic buyer, technical evaluator, and end user, without leaving Salesloft.
Workflow Automation via ZoomInfo Workflows
ZoomInfo's Workflows product (formerly RingLead Orchestrate) connects directly to Salesloft for automated list building and cadence enrollment. You define filters in ZoomInfo, such as accounts showing intent on specific topics within your ICP, and qualifying contacts automatically flow into designated Salesloft cadences.
Intent-to-cadence automation: Surge signals trigger cadence enrollment without manual intervention.
Real-time enrichment: Contact data refreshed at the point of engagement, not during stale bulk imports.
Buying committee enrollment: Multi-threaded cadences populated with org chart data.
Bi-directional sync: Engagement data from Salesloft feeds back into ZoomInfo for intent model refinement.
Turning Intent Signals into Cadence Enrollment
The most impactful workflow in the Salesloft + ZoomInfo integration starts with an intent signal and ends with a personalized cadence running against the right contacts. Here's how to set it up properly.
Step 1: Define Intent Topics That Actually Matter
ZoomInfo tracks intent across thousands of topics, but most are noise for your specific use case. The mistake teams make is monitoring broad categories like "CRM" or "sales automation" and drowning in false positives. Instead, focus on topics that correlate with your actual sales conversations.
Start with your last 20 closed-won deals. What problems were those buyers trying to solve? Map those problems to ZoomInfo's topic taxonomy. You want 5-10 topics, not 50. Teams running signal-based outreach consistently find that fewer, more precise signals outperform broad monitoring.
Step 2: Set Surge Thresholds
ZoomInfo's intent scoring uses a surge model, meaning it measures whether an account's research activity on a topic is abnormally high compared to their baseline. The default threshold catches too many accounts. Set your surge threshold to "strong" or higher to reduce noise, and combine it with firmographic filters that match your ICP criteria.
Step 3: Build the Automation in ZoomInfo Workflows
In ZoomInfo Workflows, create an automation that:
- Triggers on intent surge for your selected topics
- Filters by ICP firmographics (industry, employee count, revenue range, technology stack)
- Identifies contacts matching your target personas (title, department, seniority)
- Enriches those contacts with current contact data
- Pushes them to the appropriate Salesloft cadence
Step 4: Map Intent Topics to Specific Cadences
This is where most teams stop short. They build one "intent-triggered" cadence and route everything through it. That's a waste of the signal. If someone is researching "data integration challenges," they should get a different cadence than someone researching "sales analytics tools," even if both are relevant to your product.
Create cadence variants mapped to your top intent topic clusters. The messaging should directly reference the problem the intent signal suggests they're investigating. This is the same principle behind concept-centric personalization: the value of the signal is in the context it provides, not just the timing.
ZoomInfo intent data has a 3-7 day latency from actual research activity to signal delivery. This means a "surge" you see today reflects behavior from last week. Build your cadences with this lag in mind. Don't open with "I noticed you've been researching X this week" because the timing may feel off. Instead, reference the problem space generally: "Teams evaluating X often run into Y..."
Contact Enrichment Workflow: Getting the Right Data into Salesloft
The enrichment side of the integration determines whether your cadences actually reach people. Here's how to configure it for maximum deliverability and personalization quality.
Enrichment at Enrollment vs. Bulk Import
There are two approaches to getting ZoomInfo data into Salesloft: bulk import and enrollment-time enrichment. Bulk importing thousands of contacts monthly is the default approach, and it's the worse one. Contact data decays at roughly 30% per year. A bulk import from January is significantly degraded by April.
Instead, configure your workflows to enrich contacts at the point of cadence enrollment. This means the email address and phone number are verified against ZoomInfo's database at the moment they matter, not weeks or months earlier. Teams focused on outbound data enrichment have found this approach cuts bounce rates by 15-25% compared to bulk imports.
Fields That Matter for Personalization
Most teams pull name, title, email, and phone from ZoomInfo. That's the minimum. The enrichment fields that actually drive cadence personalization include:
| ZoomInfo Field | Salesloft Use | Personalization Value |
|---|---|---|
| Department | Cadence routing | Determines which pain points to lead with |
| Management Level | Cadence selection | VP gets strategic messaging; Director gets tactical |
| Tech Stack (via Scoops) | Custom fields | Reference specific tools they already use |
| Company Revenue | Segmentation tags | Align pricing and ROI framing to company size |
| Recent Job Change | Trigger cadences | New-in-role messaging with specific onboarding angles |
| Intent Topics | Custom fields | Ground messaging in their actual research behavior |
Mapping Custom Fields
Salesloft supports custom fields on person and account records. Map ZoomInfo enrichment data to these fields so your cadence templates can dynamically reference them. For example, a template variable like {{custom.tech_stack}} can pull the prospect's current technology into the email body without manual research.
This is where the integration starts to compound. Each additional enrichment field you map becomes a variable your cadences can use for personalization beyond the first line. The setup takes an hour. The ongoing personalization lift is permanent.
Targeting Decision-Makers: Multi-Threading with ZoomInfo Org Data
Single-threaded outreach, sending cadences to one contact per account, is the most common reason deals stall in early-stage pipeline. ZoomInfo's organizational data combined with Salesloft's account-level cadence management makes multi-threading operationally feasible.
Building the Buying Committee from ZoomInfo
For each intent-surging account, use ZoomInfo's org chart data to identify three to five contacts across different roles:
- Economic Buyer: VP or C-level who controls budget. Messaging focuses on strategic outcomes and ROI.
- Technical Evaluator: Director or senior IC who will assess your product. Messaging focuses on integration, implementation, and technical capabilities.
- End User/Champion: Manager or IC who will use the product daily. Messaging focuses on day-to-day pain relief and workflow improvement.
- Influencer: Adjacent stakeholder (often in ops or finance) who has input on the decision. Messaging focuses on cross-functional impact.
Coordinated Cadences, Not Duplicate Cadences
The critical mistake is enrolling all five contacts in the same generic cadence. Each persona needs a distinct cadence variant with messaging tailored to their role and concerns. Salesloft's account-level views let you see all active cadences on an account, so reps can coordinate timing and avoid the nightmare of three people at the same company getting identical emails on the same day.
Configure cadence rules so that the champion-level contact starts their cadence first. If they engage (open, click, reply), the economic buyer cadence activates 48 hours later with a reference to the conversation already underway. This sequencing feels natural rather than like a coordinated blast. Teams running orchestrated ABM outbound see 2-3x higher account-level response rates with this approach.
Using ZoomInfo Scoops for Timing
ZoomInfo Scoops surface events like leadership changes, funding rounds, technology purchases, and expansion plans. These aren't intent signals per se, but they're powerful engagement triggers. A new VP of Sales who just joined is 3-5x more likely to evaluate new tools in their first 90 days. A company that just raised Series B is actively investing in infrastructure. Layer these signals on top of intent data to prioritize which accounts to multi-thread first.
Cadence Personalization with ZoomInfo Data
Having the data in Salesloft is step one. Using it to create cadences that actually convert is step two. Here's where most teams leave the biggest gap.
Template Architecture for Intent-Based Cadences
Rather than writing entirely unique cadences for every intent topic, build a modular template system:
- Opening hook: References the problem space indicated by the intent signal. Variable-driven using the intent topic field.
- Pain articulation: Maps to the specific persona's version of the problem. A CFO cares about cost. A VP Engineering cares about reliability. Same intent signal, different angles.
- Proof point: Case study or metric that matches their industry and company size. Pulled from your proof library, filtered by the firmographic data ZoomInfo provides.
- Call to action: Varies by seniority. Executives get "quick conversation" asks. ICs get "see how it works" demos.
This modular approach means you can generate dozens of cadence variants from a small number of components. The targeted sequence generation principle applies: define the building blocks once, then let enrichment data assemble them per prospect.
Dynamic Fields vs. Static Segments
Salesloft supports Liquid-style template variables that pull from custom fields. Use these for:
{{company_name}}and{{first_name}}(obviously){{custom.tech_stack}}for technology references{{custom.company_revenue_range}}for sizing ROI claims{{custom.intent_topic}}for problem-space references
But be careful. Dynamic fields work well for factual inserts. They work poorly for narrative flow. "I noticed {{company_name}} is exploring {{custom.intent_topic}}" reads like a mail merge, not a human message. Use dynamic fields for the data points, but write the connective tissue as natural language that works regardless of the specific values.
Cadence Branching Based on Engagement
Salesloft's cadence rules engine lets you branch based on prospect engagement. Combine this with ZoomInfo enrichment data to create adaptive sequences:
- High intent + email open but no reply: Branch to phone step with talk track referencing the intent topic.
- High intent + no engagement after Step 3: Branch to LinkedIn touchpoint with a connection request referencing shared context.
- Multiple contacts at the same account engaging: Trigger a multi-channel escalation that coordinates across the buying committee.
ROI Optimization: Making the Integration Pay for Itself
ZoomInfo and Salesloft are both expensive. The combined spend for a mid-market team can easily exceed $100K annually. Here's how to ensure the integration delivers returns that justify the investment.
Track the Right Metrics
Most teams measure reply rates on intent-triggered cadences. That's necessary but insufficient. The metrics that actually tell you whether the integration is working:
| Metric | What It Tells You | Target Benchmark |
|---|---|---|
| Intent-to-meeting conversion rate | Whether intent signals lead to pipeline | 3-5% of surging accounts |
| Time from intent surge to first touch | Whether your workflow is fast enough | <24 hours |
| Bounce rate on enriched contacts | Whether ZoomInfo data quality is holding up | <3% |
| Multi-thread coverage per account | Whether you're reaching the committee | 3+ contacts per target account |
| Intent-sourced pipeline $ | Revenue attribution to the integration | 5-8x combined tool cost |
Reduce ZoomInfo Credit Waste
ZoomInfo charges per contact reveal and per enrichment API call. The integration can burn through credits fast if you're enriching every contact that matches a broad filter. Optimize credit spend by:
- Filtering before enrichment: Only enrich contacts at accounts that meet your full ICP criteria AND show intent. Sequence matters: apply the free filters (firmographics) first, then spend credits on the qualified subset.
- Caching enrichment data: If a contact was enriched within the last 30 days, skip re-enrichment. This requires a refresh cadence strategy, but it can cut credit consumption by 40%.
- Prioritizing high-value contacts: Don't spend credits enriching the entire org. Focus on the three to five roles in your buying committee and skip the rest.
A/B Test Intent-Based vs. Cold Cadences
Run a controlled comparison: intent-triggered cadences with ZoomInfo enrichment vs. your standard cold outbound cadences. Measure not just reply rates but pipeline creation and deal velocity. Most teams see 2-4x higher meeting rates from intent-triggered sequences, which is the data point you need to justify the integration spend to leadership.
Document these results rigorously. Teams that A/B test sequences properly can quantify the exact dollar value of each ZoomInfo intent signal that converts to pipeline.
Where the Integration Falls Short
No integration is seamless, and the Salesloft + ZoomInfo connection has real gaps that you should plan around.
Intent Data Isn't Predictive Enough on Its Own
ZoomInfo's intent signals tell you that an account is researching a topic, not that they're ready to buy. Roughly 60-70% of accounts that surge on relevant topics never enter a buying cycle. Intent is a prioritization signal, not a purchase signal. Teams that treat every intent spike as a hot lead burn rep capacity on accounts that were just doing casual research.
Combine intent with other signals: website visits, content downloads, product trials, or product usage data. Accounts showing intent AND first-party engagement are 5-10x more likely to convert than intent alone.
Enrichment Gaps Are Common
ZoomInfo's coverage varies significantly by market segment. Enterprise accounts (10,000+ employees) typically have 80-90% coverage. SMB accounts (under 200 employees) may have 40-60% coverage. If your ICP skews toward smaller companies, plan for enrichment gaps and have a fallback data source configured.
The Integration Is One-Directional for Context
ZoomInfo data flows into Salesloft, but engagement context from Salesloft doesn't meaningfully flow back into ZoomInfo's models. This means your intent scoring doesn't get smarter based on which signals actually led to meetings. You're relying entirely on ZoomInfo's generic model rather than one tuned to your specific buyer behavior.
No Native Orchestration Layer
The integration handles data transfer and basic automation, but it doesn't provide a true orchestration layer. If you want to coordinate intent signals, enrichment data, CRM records, cadence engagement, and first-party signals into a unified decision framework, you'll need to build that yourself or bring in additional tooling.
FAQ
The basic integration (contact push, enrichment mapping) takes 2-4 hours. Building intent-triggered workflow automations with proper cadence routing and custom field mapping typically requires 1-2 weeks of configuration and testing. Plan for an additional 2-3 weeks to optimize intent topic selection and cadence variants based on initial performance data.
The standard integration supports manual contact export and basic enrichment. For the intent-to-cadence automation described in this guide, you need ZoomInfo Workflows (or the equivalent automation tier in your ZoomInfo plan). This is a separate product with its own pricing. Check with your ZoomInfo rep whether your current plan includes it.
Start with 5-8 topics directly tied to the problems your product solves. Expand only after you've validated that initial topics generate qualified pipeline. Teams monitoring 50+ topics typically see worse results than teams monitoring 8 precise ones, because the noise overwhelms the signal and reps lose trust in the data.
Yes. When an inbound lead enters Salesloft (via CRM sync or direct import), ZoomInfo enrichment can fill in missing fields before cadence enrollment. This is particularly valuable for leads who submitted minimal form data. Combine this with automated inbound qualification for maximum impact.
Salesloft typically runs $100-150 per user per month for teams of 10-30 reps. ZoomInfo's pricing varies widely but expect $15,000-40,000 annually depending on credit volume and product tier. Combined, a 15-person sales team might spend $80,000-120,000 annually on both platforms. The integration itself doesn't add cost, but you need the right product tiers on both sides.
Clay and ZoomInfo serve overlapping but distinct purposes. ZoomInfo provides proprietary intent data that Clay doesn't generate natively. Clay offers more flexible waterfall enrichment across multiple data providers. Many teams use both: ZoomInfo for intent signals and Clay for multi-source enrichment recipes. The best approach depends on whether intent data or enrichment flexibility is your bigger gap.
What Changes at Scale
The Salesloft + ZoomInfo integration works well when you're running 5-10 intent-triggered cadences against a few hundred accounts. At 50 cadences across thousands of accounts, the operational complexity changes fundamentally.
The first thing that breaks is context consistency. ZoomInfo tells you what an account is researching. Salesloft tells you how contacts are engaging with your outreach. Your CRM tells you the deal history. Your product analytics tell you about trial activity. But none of these systems talk to each other in a way that gives any single workflow the full picture. Your intent-triggered cadence doesn't know the prospect already had a demo last quarter. Your enrichment workflow doesn't know the account's champion just left the company.
The second thing that breaks is cadence management. When you have dozens of intent-topic-to-cadence mappings, persona variants for each, and branching logic based on engagement, the combinatorial explosion becomes unmanageable in Salesloft's native UI. Teams end up with 200+ cadences, half of which are outdated, and reps default back to their three favorites.
What you actually need at this stage is a unified context layer that sits across your intent data, enrichment sources, CRM, and engagement platform. Instead of building point-to-point logic between ZoomInfo and Salesloft, you need a system that maintains a continuously updated picture of every account and contact, combining intent signals, enrichment data, engagement history, and first-party behavior into a single context graph.
This is the problem that platforms like Octave are built to solve. Rather than treating each ZoomInfo intent signal as an isolated trigger, Octave maintains unified GTM context that any downstream tool, whether Salesloft, your CRM, or your Clay workflows, can query for the full picture. The intent signal becomes one input among many, weighted and correlated with everything else you know about the account. The result is cadence enrollment decisions that account for the complete relationship history, not just the latest Bombora spike.
Conclusion
The Salesloft + ZoomInfo integration is one of the higher-leverage configurations in the modern outbound stack. Intent signals provide timing. Enrichment data provides targeting. Cadence automation provides execution. When all three are connected properly, you get a system that consistently puts relevant messages in front of the right people at approximately the right moment.
The key word is "approximately." Intent data is directional, not precise. Enrichment data decays. Cadence personalization via template variables gets you 70% of the way to genuinely relevant messaging. The teams that extract the most value from this integration are the ones that treat it as infrastructure, not magic. They invest in intent topic refinement, custom field mapping, cadence architecture, and ongoing metric tracking. They combine ZoomInfo signals with first-party data to reduce false positives. And they build workflows that can scale beyond the first hundred accounts without requiring a full-time admin to maintain.
Start with the intent-to-cadence workflow described in this guide. Validate it against a controlled baseline. Then expand systematically, adding persona variants, multi-threading, and engagement-based branching as you prove each layer's impact. The integration rewards precision over breadth, every time.