Clu Now Integrates with Clay, HubSpot, and 12 More Tools

We've expanded our integration ecosystem. Clu now connects natively with tools across your GTM stack - including HubSpot, Salesforce, and more. Seamless data enrichment across your entire stack.

Set up once, and enriched data flows automatically wherever you need it.

New Integrations

Clay

Clay users can now enrich with Clu's waterfall enrichment directly in their Clay tables, through Clay's HTTP API enrichment.

What it does:

• Call the Clu API from a Clay HTTP API column
• Query 25+ data providers through one API
• Get verified emails and phone numbers
• Pay only for successful email and phone enrichments

How to set up:

1. In Clay, add an enrichment and search for HTTP API
2. Point it at the Clu API
3. Add your Clu API key
4. Use in any enrichment column

Clay + Clu = waterfall enrichment without building custom integrations.

HubSpot

Native HubSpot integration for CRM-triggered enrichment.

What it does:

• Auto-enrich new contacts on creation
• Enrich when contacts enter specific lists/workflows
• Update existing contacts with fresh data
• Write directly to HubSpot contact properties

How to set up:

1. Go to Clu Settings > Integrations
2. Click Connect HubSpot
3. Authorize via OAuth
4. Configure enrichment triggers
5. Map Clu fields to HubSpot properties

No more manual exports and imports. Leads enrich automatically.

Salesforce

Managed package for Salesforce enrichment.

What it does:

• enrich leads and contacts from within Salesforce
• Trigger enrichment via Process Builder or Flow
• Bulk enrich via list views
• Real-time enrichment on record creation

How to set up:

1. Install Clu package from AppExchange
2. Configure API credentials in Setup
3. Add enrichment button to page layouts
4. Create Flow triggers for automation

Works with Salesforce Classic and Lightning.

Outreach

Clu does not sync with Outreach. Enriched data reaches Outreach prospects through a CSV.

What it does:

• Get verified emails and phone numbers onto Outreach prospects
• Keep prospect data fresh by re-enriching and re-importing

How to set up:

1. Enrich a lead list in Clu
2. Export it as a CSV
3. Import the CSV into Outreach
4. Map the columns to Outreach prospect fields

Salesloft

Add the people your agents find to Salesloft cadences.

What it does:

• Create/update Salesloft people with enriched data
• Add to cadences based on enrichment triggers
• Keep contact information current
• Track enrichment in Salesloft activity

How to set up:

1. Connect Salesloft in Clu integrations
2. Authorize via OAuth
3. Configure field mappings
4. Enable sync preferences

Apollo

Yes, you can use Clu alongside Apollo: export a CSV from Apollo and import it into Clu.

What it does:

• Verify Apollo contacts through Clu
• Fill Apollo data gaps with waterfall enrichment
• Compare Apollo emails to Clu for validation
• Best of both: Apollo's database + Clu's verification

Use Apollo for prospecting, Clu for verification and gap-filling.

Pipedrive

CRM enrichment for Pipedrive users, through a CSV. Clu does not sync with Pipedrive.

What it does:

• Export your Pipedrive contacts as a CSV
• Enrich them in a Clu lead list
• Export the enriched list as a CSV
• Import it back into Pipedrive to fill missing contact info and firmographic fields

Pipedrive + Clu keeps your pipeline data complete.

Zapier

Clu has no Zapier app. To get enriched data into other apps, use a CSV or the API.

What to use instead:

• Export an enriched list as a CSV and import it into the other app
• Call the Clu REST API from your own workflows (Pro and up)

Examples without Zapier:

• Typeform responses CSV → Clu enrich → HubSpot contacts
• Google Sheets row → Clu enrich → Salesforce lead

Additional Integrations

Also now supported:

For any other tool, export a CSV from Clu and import it there.

Integration Deep Dives

Clay + Clu: Waterfall Enrichment in Your Tables

Clay is a powerful prospecting workspace, but its built-in enrichment relies on individual provider connections. Each provider has coverage gaps. By adding Clu as a Clay enrichment source, you get waterfall enrichment across 25+ providers in a single column.

The typical Clay workflow before Clu: add a person finder column (Apollo), then a separate email finder (Hunter), then a phone finder (Lusha). Three columns, three credits, and you still have gaps where none of the three had data.

With Clu as your enrichment source, one column cascades through all 25+ providers. If Apollo doesn't have the email, Clu queries Hunter, then Lusha, then 12 more providers. The result is a single enriched column with 85-95% coverage instead of 50-70%.

Setup takes under 5 minutes. Add an HTTP API enrichment column in Clay, call the Clu API with your API key, and map the input fields (name, company, LinkedIn URL). Every new row in your Clay table gets enriched automatically. For a detailed walkthrough, see our Clay API integration guide.

HubSpot + Clu: CRM-Triggered Enrichment

The HubSpot integration is built for RevOps teams who want enrichment to happen without anyone touching a button. The most common setup is auto-enrichment on contact creation: when a lead fills out a form, the Clu integration fires immediately and writes verified email, phone, company size, industry, and ICP score back to the contact record.

Beyond auto-enrichment, the integration supports three workflows that HubSpot data enrichment teams use daily:

1. List-based enrichment: Build a HubSpot list (e.g., "Contacts missing phone number"), trigger Clu enrichment for the entire list, and watch the gaps fill in bulk.
2. Lifecycle-based triggers: Enrich contacts when they move from Subscriber to MQL. This avoids spending credits on low-intent contacts and focuses enrichment budget where it matters.
3. Scheduled re-enrichment: Set a quarterly workflow to re-verify and refresh contacts that haven't been updated in 90+ days. This fights data decay automatically.

Field mapping is fully customizable. Map Clu's verified_email to HubSpot's email property, direct_dial to a custom phone field, and company_revenue to a custom company property. All mappings are configured once during setup and apply to every enrichment going forward.

Salesforce + Clu: Enterprise-Grade Enrichment

The Salesforce managed package supports both Lightning and Classic environments. Unlike lightweight API integrations that require engineering resources, the managed package installs from AppExchange and configures through Salesforce Setup with no code.

Key capabilities for Salesforce enrichment:

• One-click enrichment button on Lead and Contact page layouts. Reps click "Enrich" on any record and get verified data in seconds.
• Flow-triggered bulk enrichment. Create a scheduled Flow that enriches all Leads created in the last 7 days with missing email or phone fields.
• Process Builder automation. Trigger enrichment when a Lead is converted to a Contact, ensuring the Contact record starts with complete, verified data.
• Custom object support. Map enrichment results to custom objects if your org uses a non-standard data model.

The package respects Salesforce governor limits and processes enrichment asynchronously for bulk operations. For enterprise teams running 10,000+ enrichments per month, the Salesforce integration handles the volume without performance degradation.

Zapier and Tools Without a Native Connection

Clu has no Zapier app. For tools it doesn't connect to natively, the route is a CSV or the Clu REST API. The workflows teams ask about fall into three categories:

Inbound capture workflows: A lead fills out a Typeform, completes a Calendly booking, or submits a request via Intercom. Export those contacts as a CSV, enrich them in a Clu lead list, and push the enriched records to HubSpot or Salesforce, or export a CSV for any other CRM or sequencing tool.

Cross-platform sync: Enriched Clu data flows to Google Sheets for reporting and Slack channels for notifications. For project management tools like Asana or Monday.com, export a CSV for follow-up task creation.

Multi-step automation: Chain Clu enrichment with other actions in your own code through the REST API. For example: new Stripe customer created, enrich the contact, then pass the verified record to the next step.

The REST API needs a Clu API key, issued on Pro and up.

API for Custom Integrations

For tools without native integration, use our API:

POST https://api.cleanlist.ai/v1/enrich
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
 
{
  "records": [
    {
      "first_name": "John",
      "last_name": "Smith",
      "company": "Acme Corp"
    }
  ],
  "fields": ["email", "phone", "title", "company_size"]
}

Response:

{
  "results": [
    {
      "input": {"first_name": "John", "last_name": "Smith", "company": "Acme Corp"},
      "enriched": {
        "email": "john.smith@acmecorp.com",
        "email_verified": true,
        "phone": "+1-555-123-4567",
        "phone_type": "direct",
        "title": "VP of Sales",
        "company_size": "201-500",
        "confidence_score": 95
      },
      "credits_used": 1
    }
  ]
}

API documentation: docs.cleanlist.ai/api

Integration Recipes

Recipe 1: Inbound lead enrichment

Trigger: New HubSpot contact created Action: Clu enrichment Result: Contact updated with verified email, phone, firmographics

HubSpot Contact Created → Clu Enrich → HubSpot Contact Updated

Recipe 2: ABM list building

Trigger: Add company to Salesforce campaign Action: Clu find contacts matching criteria Result: Decision-maker contacts added to campaign

Salesforce Campaign → Clu People Search → Salesforce Campaign Members

Recipe 3: CRM hygiene

Trigger: Weekly scheduled job Action: Clu verify all contacts updated 90+ days ago (fighting data decay) Result: Invalid contacts flagged, valid contacts refreshed

Scheduled Trigger → Clu Bulk Verify → CRM Update + Slack Alert

Recipe 4: Clay waterfall

Trigger: New row in Clay table Action: Clu enrichment through an HTTP API column Result: Waterfall finds best email from 25+ sources

Clay Table Row → Clu Enrichment → Clay Enriched Data

Frequently Asked Questions

How long does it take to set up an integration?

Most native integrations (HubSpot, Salesforce) take 5-15 minutes to connect and configure. OAuth-based connections require a single authorization click. Field mapping is the most time-consuming step, but Clu provides default mappings for standard CRM fields that work out of the box.

Can I use multiple integrations at the same time?

Yes. Many teams use 3-4 integrations simultaneously. A common setup: HubSpot for CRM enrichment, the Clu API in Clay for prospecting workflows, Lemlist for sequence sync, and CSV exports for niche tools without a native connection. Each integration operates independently with its own triggers and field mappings.

Do integrations count against my credit balance?

Yes. Each enrichment triggered by an integration uses credits from your Clu account, following the same pricing as manual enrichment. Partial enrichment (email only) uses 1 credit per record. Full enrichment (email + phone + firmographics) uses 11 credits. You can set credit limits per integration to control spend.

What happens if an integration fails or loses connection?

Clu monitors integration health and sends alerts if a connection drops. Failed enrichments are queued and retried automatically when the connection is restored. For OAuth-based integrations, you may need to re-authorize if your CRM access token expires. All failed records are logged in the Clu dashboard so nothing falls through the cracks.

What's Next

Coming Q1 2026:

• LinkedIn Sales Nav: Direct enrichment from saved lists
• Slack: Enrich contacts via Slack command
• Chrome extension: Enrich from any webpage

Get Started with Integrations

1. Log into Clu
2. Go to Settings > Integrations
3. Connect your tools
4. Configure triggers and mappings
5. Watch data flow automatically

Questions about integrations? Contact support@cleanlist.ai or check docs.cleanlist.ai.

Your GTM stack should work together. Clu integrations make enrichment invisible - data flows where it needs to, automatically. Connect your tools and start enriching.