Databar Salesforce Integration: Setup Guide
A new lead hits Salesforce from your website form. Name. Email. Company. That is the entire record. Your SDR opens it, sees three populated fields out of twenty, and starts Googling. Five minutes later, they have a LinkedIn profile and a rough guess at company size. Multiply that by 80 new leads a day and your team is burning hours on manual research that should happen automatically.
The Databar Salesforce integration fixes this by enriching every new lead and contact the moment it enters your CRM. Verified emails, phone numbers, company data, tech stack, firmographics -- all populated before your rep opens the record.
Three Ways to Connect Databar to Salesforce
There is no single "right" method. The best approach depends on your team's technical skill, volume, and how much control you need:
Method | Best For | Setup Time | Technical Skill |
|---|---|---|---|
Zapier | Small teams, quick setup, under 5K leads/mo | 15 minutes | Low (no code) |
n8n | High volume, self-hosted, cost-conscious teams | 1-2 hours | Medium (API comfort) |
Direct API | Enterprise teams with custom requirements | 2-4 hours | High (developer needed) |
All three connect to the same Databar API and access the same 100+ data providers. Enrichment quality is identical. What changes is the automation layer between Salesforce and Databar.
Option 1: Databar + Salesforce via Zapier
Fastest path. No code, no server, no maintenance. If your lead volume stays under 5,000 per month and your team does not have a developer, start here.
Step 1: Set Up the Salesforce Trigger
Create a new Zap in Zapier. Set the trigger app to Salesforce and choose "New Record" as the trigger event. Select the object type: Lead, Contact, or Account depending on which records you want to enrich.
For most teams, triggering on new Lead creation delivers the highest impact. Leads are typically the sparsest records in Salesforce because they come from forms and imports with minimal fields.
Step 2: Add the Databar Enrichment Action
Add a "Webhooks by Zapier" action. Configure it as a Custom Request:
Method: POST
URL:
https://api.databar.ai/api/v1/enrichment/runHeaders:
Authorization: Bearer YOUR_API_KEYandContent-Type: application/jsonBody: Map Salesforce fields to Databar's parameters
Example request body for contact enrichment:
Step 3: Update the Salesforce Record
Add a third step: Salesforce "Update Record." Map the enriched fields from Databar's response to the corresponding Salesforce fields. Phone number to Phone, employee count to NumberOfEmployees, industry to Industry, and so on.
The entire zap runs in under 30 seconds. A lead enters Salesforce, gets enriched through Databar's waterfall enrichment (cascading through multiple providers), and the record updates with verified data. Your rep opens a fully populated record.

Option 2: Databar + Salesforce via n8n
For teams processing more than 5,000 leads per month, n8n eliminates per-task pricing that makes Zapier expensive at scale. Self-hosted n8n runs unlimited executions for the cost of a small server.
Set Up the Salesforce Webhook Trigger
In Salesforce, create an Outbound Message or use Flow Builder to fire a webhook when a new Lead or Contact is created. Point the webhook at your n8n instance's webhook URL.
Alternatively, use n8n's Salesforce node with polling: it checks for new records on a schedule (every 1-5 minutes) and processes any new ones found.
Build the Enrichment Workflow
The n8n workflow follows this pattern:
Salesforce Trigger (webhook or polling)
HTTP Request Node calling Databar's enrichment API
IF Node checking if enrichment returned results
Salesforce Node updating the record with enriched data
Error Handler logging failures for retry
Add a Split In Batches node if you are processing backlog records. This prevents either API from getting overwhelmed with concurrent requests.
Handle Rate Limits and Errors
Configure the HTTP Request node with 3 retries and 2-second backoff. Salesforce's API has its own rate limits (typically 15,000 API calls per 24-hour period for Enterprise Edition). Space your update calls accordingly and monitor API usage in Salesforce Setup.
Option 3: Direct API Integration
For enterprise Salesforce orgs with a developer on staff, a direct integration gives you the most control. Build Apex triggers or Salesforce Flows that call Databar's API natively.
Apex Trigger Approach
Create an Apex trigger on Lead or Contact that fires an HTTP callout to Databar on record creation. Salesforce requires callouts to be asynchronous (via @future methods or Queueable Apex), so the enrichment runs in the background and updates the record when results return.
Key considerations:
Named Credentials: Store your Databar API key as a Salesforce Named Credential, not hardcoded in Apex
Callout limits: Salesforce limits async callouts per transaction. Batch your enrichment calls for bulk imports
Governor limits: Be aware of Salesforce's DML and callout limits per transaction (100 callouts, 150 DML operations)
Retry logic: Build retry handling for failed enrichment calls using Platform Events or scheduled Apex
Salesforce Flow Approach
For a low-code option within Salesforce itself, use Flow Builder with an HTTP Callout action (available since the Winter '23 release). Build a Record-Triggered Flow that fires when a Lead is created, calls Databar's API, and updates the record with the response.
This approach skips Apex entirely and is maintainable by Salesforce admins. The tradeoff: less flexibility in error handling and retry logic compared to Apex.

Salesforce Field Mapping for Databar Enrichment
Getting field mapping right is critical. Mismatched fields mean enriched data lands in the wrong place or gets lost entirely.
Standard Salesforce Fields
Databar Response Field | Salesforce Lead Field | Salesforce Contact Field |
|---|---|---|
phone | Phone | Phone |
mobile_phone | MobilePhone | MobilePhone |
title | Title | Title |
employee_count | NumberOfEmployees | (on Account) |
industry | Industry | (on Account) |
annual_revenue | AnnualRevenue | (on Account) |
website | Website | (on Account) |
linkedin_url | Custom field | Custom field |
tech_stack | Custom field | (on Account, custom) |
Custom Fields You Should Create
Salesforce's standard fields do not cover everything Databar returns. Create these custom fields to capture the full enrichment output:
LinkedIn_URL__c (URL field on Lead and Contact)
Tech_Stack__c (Long Text Area on Account)
Enrichment_Date__c (Date field on Lead and Contact)
Enrichment_Source__c (Text field: tracks which provider returned the data)
Data_Quality_Score__c (Number field: your internal quality rating)
Enrichment_Date__c matters most. It lets you identify stale records that need re-enrichment. Filter for records where Enrichment_Date__c is older than 90 days and run them through a refresh cycle. Automated CRM cleaning depends on knowing when data was last verified.
Trigger-Based Enrichment Strategies for Salesforce
Not every record needs enrichment at the same moment. Trigger-based strategies let you enrich the right records at the right time.
Trigger 1: New Lead Creation
The most common trigger. Every new Lead gets enriched immediately. This covers inbound leads (form fills, chat, imports) and means reps never open an empty record.
Trigger 2: Lead Conversion to Contact
When a Lead converts to a Contact and Account, re-enrich with deeper company data. The Lead stage needs basic qualification data (email, phone, company size). The Contact/Account stage benefits from detailed firmographics (revenue, funding, tech stack, org chart).
Trigger 3: Opportunity Stage Change
When a deal moves to a qualified stage, trigger enrichment on all contacts associated with the Account. Pull fresh data to support the sales conversation: recent funding rounds, new hires, technology changes. This gives reps current intelligence at the moment it matters most.
Trigger 4: Scheduled Re-Enrichment
Run a weekly or monthly batch job that re-enriches records older than 90 days. Contact data decays at 30% per year. Without periodic re-enrichment, your Salesforce data becomes unreliable within a few months. Use batch enrichment for scheduled runs and real-time enrichment for trigger-based events.

Common Pitfalls When Integrating Databar With Salesforce
Teams hit the same issues repeatedly. Avoid these before they cost you time.
Overwriting manually entered data. Build logic that checks if a field already has a value before overwriting. If a rep manually entered a phone number, your automation should not replace it with an enriched result that might be less accurate. Use "update if blank" logic.
Ignoring Salesforce API limits. Enterprise Edition gets 15,000 API calls per 24 hours. A bulk import of 10,000 leads with enrichment and update calls can consume a big chunk of that limit. Monitor usage in Salesforce Setup under System Overview.
Not handling enrichment failures. Not every record will return enriched data. Build a fallback path that tags un-enrichable records so they do not block your workflow or trigger infinite retry loops.
Skipping email verification. Enriched emails are not always deliverable. Run every enriched email through verification before using it for outbound. Databar's waterfall enrichment includes verification as part of the cascade, so verified results come back by default when you use waterfalls.
Also Interesting
Frequently Asked Questions: Databar Salesforce Integration
Does Databar have a native Salesforce integration?
Databar connects to Salesforce through its REST API using Zapier, n8n, or direct API calls. There is no managed package to install. This gives you full control over which records get enriched, which fields get updated, and when enrichment triggers fire.
How fast is enrichment when a new Salesforce lead is created?
A single enrichment call returns results in 5-15 seconds. Waterfall enrichment with multiple providers takes slightly longer since providers are called sequentially. With Zapier or n8n, the full cycle (trigger, enrich, update) typically completes in under 60 seconds.
Can I enrich existing Salesforce records, not just new ones?
Yes. Export your existing records, run them through Databar's batch enrichment, and import the enriched data back into Salesforce. For ongoing re-enrichment, set up a scheduled workflow that processes records older than 90 days.
How do I handle Salesforce API limits with enrichment automation?
Monitor your API usage in Salesforce Setup. For bulk operations, use the Salesforce Bulk API (2.0) which has separate, higher limits. Space out enrichment calls during off-peak hours. For real-time triggers, the API call volume is usually low enough to stay well within limits.
What Salesforce editions support the Databar integration?
Any edition that supports API access works with Databar: Professional (with API add-on), Enterprise, Unlimited, and Developer editions. The Zapier approach works with any edition since Zapier handles the API connection.
Can I enrich Salesforce Account records, not just Leads and Contacts?
Yes. Use the company domain or company name to trigger company enrichment through Databar. Map the results (employee count, revenue, industry, tech stack) to Account fields. Especially useful for ABM programs where Account-level data drives targeting.
How much does the Databar Salesforce integration cost?
Databar uses pay-as-you-go credit pricing with no minimums or annual contracts. Total cost depends on enrichment volume and which data points you need. The integration itself (via Zapier, n8n, or API) has no extra Databar fee. Factor in your Zapier or n8n costs separately if applicable.
Connect Databar to Salesforce and Enrich Automatically (Databar Salesforce Integration)
Your Salesforce reps should not spend time Googling leads. The Databar Salesforce integration enriches every new record with verified data from 100+ providers -- automatically, within seconds of creation.
Pick your integration method (Zapier for speed, n8n for scale, direct API for control), map your fields, set your triggers. Start with a free Databar account and have your first enrichment automation running today.
Also Interesting
Recent articles
See all









