Setting Up Your First Integration
Connect LeadConduit to your CRM, email system, or other business tools. This guide walks through your first integration setup with best practices for success.
๐ You Are Here
You have a flow receiving leads, and now you need to send them somewhere useful. Whether it's a CRM, email platform, or custom endpoint, this guide shows you how to set up reliable delivery.
๐ฏ What You'll Learn
- Choosing the right integration
- Step-by-step configuration
- Testing your connection
- Troubleshooting common issues
- Best practices for reliability
๐ค Choosing Your First Integration
Common First Integrations
For Sales Teams:
- Salesforce
- HubSpot
- Pipedrive
- Custom CRM webhook
For Marketing:
- Mailchimp
- ActiveCampaign
- Constant Contact
- Marketing automation
For Call Centers:
- Five9
- Velocify
- Phone burner
- Custom dialer
For Testing:
- Webhook.site
- RequestBin
- Custom endpoint
๐ Setting Up a Webhook Integration
We'll start with a webhook - the most flexible integration type.
Step 1: Add Integration Step
- Open your flow
- Click Add Step after your source
- Select Delivery
- Choose Custom Webhook
Step 2: Configure Endpoint
Enter your destination details:
Name: My CRM Webhook
URL: https://api.mycrm.com/leads
Method: POST
Content-Type: application/json
Step 3: Add Authentication
Most APIs require authentication:
API Key in Header:
Header Name: X-API-Key
Header Value: your-api-key-here
Bearer Token:
Header Name: Authorization
Header Value: Bearer your-token-here
Step 4: Map Your Fields
Connect LeadConduit fields to API fields:
LeadConduit Field โ API Field
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
email โ contact_email
phone_1 โ phone_number
first_name โ given_name
last_name โ family_name
state โ location_state
Step 5: Configure Response Parsing
Tell LeadConduit how to read the response:
Success Indicator: status_code = 200
Lead ID Location: response.body.id
Error Message: response.body.error
๐ง Example: Salesforce Integration
Step 1: Add Salesforce Step
- Click Add Step
- Select Delivery
- Choose Salesforce
- Click Add Salesforce
Step 2: Authenticate
- Click Connect to Salesforce
- Log in with Salesforce credentials
- Authorize LeadConduit access
- Connection confirmed!
Step 3: Configure Lead Creation
Object Type: Lead
Field Mappings:
email โ Email
phone_1 โ Phone
first_name โ FirstName
last_name โ LastName
company โ Company (required)
state โ State
Required Fields:
- LastName (map from last_name)
- Company (set default if not collected)
Step 4: Set Options
- Duplicate Handling: Update existing
- Assignment Rule: Use active rule
- Owner: Round-robin or specific user
- Lead Source: Set to "Web" or dynamic
๐ง Example: Mailchimp Integration
Step 1: Add Mailchimp Step
- Add Step โ Delivery โ Mailchimp
- Name it "Add to Newsletter"
Step 2: Connect Account
- Click Connect Mailchimp
- Log in to Mailchimp
- Authorize access
- Select your account
Step 3: Configure List
List Selection:
- Choose your audience/list
- Or map dynamically based on data
Field Mappings:
email โ EMAIL (required)
first_name โ FNAME
last_name โ LNAME
phone_1 โ PHONE
state โ STATE
Subscription Settings:
- Status: Subscribed
- Marketing permissions: Based on consent
- Tags: Add based on source/campaign
๐งช Testing Your Integration
Step 1: Use Test Mode
Before going live:
- Enable Test Mode on the integration
- Send a test lead
- Verify it appears correctly
- Check field mapping
Step 2: Send Test Lead
From your flow:
- Click Test button
- Fill in sample data
- Submit test lead
- Check the Events tab
Step 3: Verify Delivery
Check your destination:
- Lead appears in CRM?
- Contact added to email list?
- All fields mapped correctly?
- No duplicate created?
Step 4: Test Edge Cases
Don't forget to test:
- Missing optional fields
- Invalid data formats
- Duplicate submissions
- API errors/timeouts
๐ซ Common Issues and Solutions
"Authentication Failed"
Symptoms: 401 or 403 errors
Solutions:
- Re-authenticate the integration
- Check API key hasn't expired
- Verify permissions are correct
- Try in a private browser
"Required Field Missing"
Error: "Company is required"
Solutions:
- Map the field if available
- Set a default value
- Make field required in your source
- Use conditional logic
"Invalid Field Value"
Error: "State must be 2-letter code"
Fix with transformation:
California โ CA
Texas โ TX
New York โ NY
"Duplicate Record"
Solutions:
- Enable update mode
- Set unique identifier
- Check duplicate settings
- Use upsert operation
๐ก Best Practices
Field Mapping
Do:
- Map all available fields
- Use consistent naming
- Document custom mappings
- Test edge cases
Don't:
- Leave required fields unmapped
- Assume field formats
- Ignore case sensitivity
- Skip testing
Error Handling
Always Configure:
- Retry attempts (3-5)
- Retry delays (exponential)
- Failure notifications
- Backup delivery method
Performance
Optimize for Speed:
- Minimize field mappings
- Use batch where available
- Enable caching
- Monitor response times
๐ฏ Integration Checklist
Before activating:
- Authentication working
- All required fields mapped
- Test lead delivered successfully
- Response parsing configured
- Error handling set up
- Retry logic enabled
- Documentation complete
- Team members trained
๐ Next Steps
After Your First Integration
Add More Integrations
- Email verification
- Phone validation
- Duplicate checking
Configure Advanced Features
- Conditional routing
- Multi-step delivery
- Failover options
Monitor Performance
- Set up alerts
- Track success rates
- Optimize slow steps
Common Second Integrations
Data Quality:
- Email verification
- Phone validation
- Address standardization
Compliance:
- TrustedForm
- DNC checking
- Age verification
Enhancement:
- Demographic append
- Lead scoring
- Social matching
๐ Related Documentation
- Configuring Delivery - Advanced delivery options
- Data Mapping - Complex field transformations
- Integration Directory - All available integrations
๐ฏ Integration Success: Your first integration is the gateway to automated lead flow. Take time to test thoroughly - a well-configured integration saves hours of manual work!
Comments
0 comments
Please sign in to leave a comment.