Overloop

Overloop Salesforce integration

Connect Salesforce to Overloop, map supported fields and record types, and use CRM prospect data in email and LinkedIn outreach.

See Salesforce in action

01 Choose records Scope defined

02 Map fields Rules reviewed

03 Review setup Workflow ready

Records mapped fields

Sent emails logged via BCC

Setup guided workflow

What does the Overloop Salesforce integration do?

The native Overloop Salesforce integration lets Enterprise teams connect the two products, map supported fields and record types, and use CRM prospect data in Overloop workflows. Teams can create leads, contacts, organizations, or opportunities with one-way workflow steps, or enable the scheduled two-way sync for mapped prospect records.

Plan and scope: Salesforce CRM integration is available on Enterprise only. Review the official CRM integration guide and CRM integration pricing and plan details before implementation.

How to connect Overloop and Salesforce

Open the integrations settings

On an Enterprise workspace, go to Settings, open Features & Integrations, and select Salesforce.
Authorize the connection

Follow the on-screen authorization flow and have a Salesforce administrator review the requested access and object permissions.
Map your fields

Email, first name, and last name map automatically. Match other supported Overloop fields to the Salesforce fields and record types approved by RevOps.
Map users and email logging

Match Overloop prospect owners to Salesforce users. Add the appropriate Salesforce BCC address if you want sent Overloop emails logged in the CRM.
Start prospecting

Test a small record set, verify field behavior and email logging, then use eligible prospects in an email and LinkedIn sequence.

Why teams sync Overloop with Salesforce

Less manual data entry

Configured field mapping can reduce manual entry for supported prospect records. It does not guarantee that every lead, contact, opportunity, activity, or custom object moves both ways.

Controlled email logging

Configure a Salesforce BCC address to log sent Overloop emails. Validate any additional engagement events in your workspace before using them in reporting or automation.

Multichannel outreach from CRM records

Use mapped Salesforce prospect data to prepare email and LinkedIn sequences, then review AI-drafted outreach before launch.

Defined field ownership

RevOps can define field ownership, user mapping, and record-type rules so teams know which system is authoritative for each data point.

What you can sync

Salesforce needs more governance than a simple account connection. The public Overloop documentation identifies these concrete behaviors.

One-way workflow actions. The official one-way sync guide documents Salesforce leads, contacts, organizations, and opportunities. Existing CRM prospects are not updated by this action.
Scheduled two-way sync. The official two-way sync guide documents a ten-minute schedule, email matching, no record deletion, and optional tracking-event notes.
Conflict handling. Salesforce takes precedence when the same mapped field conflicts; blank values do not overwrite existing data.
API protection. Salesforce admins can set a daily API-call ceiling for the two-way sync.

Salesforce troubleshooting checklist

Use Settings → Integrations → Salesforce → Logs to inspect failed events and their error details. Common documented causes include daily API limits, the maximum records-per-sync setting, missing object permissions, duplicate rules, required fields without values, country/state picklist formats, field-level security, and a disabled Salesforce REST API.

Resolve the underlying Salesforce permission, validation, mapping, or limit issue before retrying. The scheduled sync will retry after the error is corrected. Keep the official Salesforce error guide with the rollout runbook so RevOps can distinguish configuration errors from temporary API limits.

Who it's for

The Overloop Salesforce integration is built for Enterprise revenue teams with a Salesforce administrator or RevOps owner who can define field ownership, record types, permissions, and testing. Overloop's contact database and outreach workflows remain separate capabilities from the documented CRM sync scope.

Frequently asked questions

Is the Salesforce integration native?

Yes. Salesforce is listed as a native Overloop CRM integration for Enterprise. Setup is handled from Features & Integrations, where you authorize the connection, map supported fields, choose record types, and map prospect owners.

Does the integration sync both ways?

Yes, for configured prospect data. The documented two-way sync runs every ten minutes, matches records by email, gives Salesforce precedence in field conflicts, skips blank overwrites, and never deletes records. Test every required mapping before rollout.

What engagement data gets pushed to Salesforce?

The two-way sync can add notes when a prospect opens an email, clicks a link, visits a page, or replies. Sent emails can also be copied through the configured Salesforce BCC address. Treat opportunities and custom objects as separate, explicitly tested workflow scope.

Can I enroll Salesforce records into sequences?

You can use eligible mapped prospect data in Overloop email and LinkedIn workflows. Test a small record set first, and do not assume every sequence touch will be logged beyond the sent-email behavior configured through BCC.

How do I troubleshoot a failed Salesforce sync?

Open Settings → Integrations → Salesforce → Logs and review the failed event. The official troubleshooting guide covers API limits, permissions, duplicate rules, required fields, field security, and REST API access. Fix the underlying issue before retrying.

Is the integration GDPR-compliant?

Overloop publishes information about its data practices on the Overloop data protection and GDPR information. Your organization remains responsible for lawful basis, permissions, field selection, retention, notices, and Salesforce access controls.

What can a one-way Salesforce workflow create?

The one-way sync guide documents Salesforce leads, contacts, organizations, and opportunities. It creates a new CRM record from Overloop and does not update a prospect already present in Salesforce.

How long does setup take?

Setup time depends on Enterprise access, Salesforce permissions, field mapping, record types, user mapping, and testing. Involve your Salesforce administrator, validate a small record set, and document which system owns each field before a wider rollout.