Salesforce Data Enrichment Workflow

​

Template

Download the following json file and import it to a new n8n workflow:

​

Overview

This n8n workflow monitors your Salesforce instance for new leads and automatically enriches them with missing contact information. When a lead is created, the workflow:

1. Detects the new lead via Salesforce trigger
2. Matches the lead against Explorium’s database using name and company
3. Enriches the lead with professional email addresses and phone numbers
4. Updates the Salesforce lead record with the discovered contact information

This automation ensures your sales team always has the most up-to-date contact information for new leads, improving reach rates and accelerating the sales process.

​

Key Features

• Real-time Processing: Triggers automatically when new leads are created in Salesforce
• Intelligent Matching: Uses lead name and company to find the correct person in Explorium’s database
• Contact Enrichment: Adds professional emails, mobile phones, and office phone numbers
• Batch Processing: Efficiently handles multiple leads to optimize API usage
• Error Handling: Continues processing other leads even if some fail to match
• Selective Updates: Only updates leads that successfully match in Explorium

​

Prerequisites

Before setting up this workflow, ensure you have:

1. n8n instance (self-hosted or cloud)
2. Salesforce account with:
   • OAuth2 API access enabled
   • Lead object permissions (read/write)
   • API usage limits available
3. Explorium API credentials (API Key)
4. Basic understanding of Salesforce lead management

​

Salesforce Requirements

​

Required Lead Fields

The workflow expects these standard Salesforce lead fields:

• FirstName - Lead’s first name
• LastName - Lead’s last name
• Company - Company name
• Email - Will be populated/updated by the workflow
• Phone - Will be populated/updated by the workflow
• MobilePhone - Will be populated/updated by the workflow

​

API Permissions

Your Salesforce integration user needs:

• Read access to Lead object
• Write access to Lead object fields (Email, Phone, MobilePhone)
• API enabled on the user profile
• Sufficient API calls remaining in your org limits

​

Installation & Setup

​

Step 1: Import the Workflow

​

Step 2: Configure Salesforce OAuth2 Credentials

Note: Use the same credentials for all Salesforce nodes in the workflow.

​

Step 3: Configure Explorium API Credentials

​

Step 4: Verify Node Settings

​

Step 5: Activate the Workflow

​

How It Works

​

Workflow Process Flow

​

Detailed Node Descriptions

1. Salesforce Trigger: Polls Salesforce every minute for new leads
2. Get Today’s Leads: Retrieves all leads created today to ensure none are missed
3. Loop Over Items: Processes leads in batches of 6 for efficiency
4. Match Prospect: Searches Explorium for matching person using name + company
5. Filter: Checks if a valid match was found
6. Extract Prospect IDs: Collects all matched prospect IDs
7. Enrich Contacts: Fetches detailed contact information from Explorium
8. Merge: Combines original lead data with enrichment results
9. Split Out: Separates individual enriched records
10. Update Lead: Updates Salesforce with new contact information

​

Data Mapping

The workflow maps Explorium data to Salesforce fields as follows:

Explorium Field	Salesforce Field	Fallback Logic
emails[0].address	Email	Falls back to professions_email
mobile_phone	MobilePhone	Falls back to phone_numbers[1]
phone_numbers[0]	Phone	Falls back to mobile_phone

​

Usage & Monitoring

​

Automatic Operation

Once activated, the workflow runs automatically:

​

Manual Testing

To test the workflow manually:

​

Monitoring Executions

Track workflow performance:

​

Troubleshooting

​

Common Issues

No leads are being processed

• Verify the workflow is activated
• Check Salesforce API limits haven’t been exceeded
• Ensure new leads have FirstName, LastName, and Company populated
• Confirm OAuth connection is still valid

Leads not matching in Explorium

• Verify company names are accurate (not abbreviations)
• Check that first and last names are properly formatted
• Some individuals may not be in Explorium’s database
• Try testing with known companies/contacts

Contact information not updating

• Check Salesforce field-level security
• Verify the integration user has edit permissions
• Ensure Email, Phone, and MobilePhone fields are writeable
• Check for validation rules blocking updates

Authentication errors

• Salesforce: Re-authorize OAuth connection
• Explorium: Verify Bearer token is valid and not expired
• Check API quotas haven’t been exceeded

​

Error Handling

The workflow includes built-in error handling:

• Failed matches don’t stop other leads from processing
• Each batch is processed independently
• Failed executions are logged for review
• Partial successes are possible (some leads updated, others skipped)

​

Best Practices

​

Data Quality

1. Ensure complete lead data: FirstName, LastName, and Company should be populated
2. Use full company names: “Microsoft Corporation” matches better than “MSFT”
3. Standardize data entry: Consistent formatting improves match rates

​

Performance Optimization

​

Compliance & Privacy

1. Data permissions: Ensure you have rights to enrich lead data
2. GDPR compliance: Consider privacy regulations in your region
3. Data retention: Follow your organization’s data policies
4. Audit trail: Monitor who has access to enriched data

​

Customization Options

​

Extend the Enrichment

Add more Explorium enrichment by:

1. Adding firmographic data (company size, revenue)
2. Including technographic information
3. Appending social media profiles
4. Adding job title and department verification

​

Modify Trigger Conditions

Change when enrichment occurs:

• Trigger on lead updates (not just creation)
• Add specific lead source filters
• Process only leads from certain campaigns
• Include lead score thresholds

​

Add Notifications

Enhance with alerts:

• Email sales reps when leads are enriched
• Send Slack notifications for high-value matches
• Create tasks for leads that couldn’t be enriched
• Log enrichment metrics to dashboards

​

API Considerations

​

Salesforce Limits

• API calls: Each execution uses ~4 Salesforce API calls
• Polling frequency: Consider your daily API limit
• Batch processing: Reduces API usage vs. individual processing

​

Explorium Limits

• Match API: One call per batch of leads
• Enrichment API: One call per batch of matched prospects
• Rate limits: Respect your plan’s requests per minute

​

Integration Architecture

This workflow can be part of a larger lead management system:

1. Lead Capture This Workflow Lead Scoring Assignment
2. Can trigger additional workflows based on enrichment results
3. Compatible with existing Salesforce automation (Process Builder, Flows)
4. Works alongside other enrichment tools

​

Security Considerations

• Credentials: Stored securely in n8n’s credential system
• Data transmission: Uses HTTPS for all API calls
• Access control: Limit who can modify the workflow
• Audit logging: All executions are logged with details

​

Support Resources

For assistance with:

• n8n issues: Consult n8n documentation or community forum
• Salesforce integration: Reference Salesforce API documentation
• Explorium API: Contact Explorium support for API questions
• Workflow logic: Review execution logs for debugging