By the end of this tutorial, you'll know how to choose which lemlist activities sync to Salesforce, configure how each activity type is stored, and give your sales team a complete outreach timeline inside their CRM — without switching tools.

When your sales team lives in Salesforce, they need to know what's happened with a prospect before picking up the phone or sending a follow-up. Activity sync brings every email sent, open, click, reply and call from lemlist directly into the lead's Salesforce activity timeline. AEs can pick up qualified leads with full context — without asking the SDR for a briefing.

In the Salesforce integration, open the Activities tab. You'll see a list of all lemlist event types — each can be individually enabled or disabled. Start by thinking about what your sales team actually needs to see in Salesforce, and only enable those.

Toggle each activity type on or off based on what's useful for your team. Email Sent, Reply Received, and Interested are the highest-value signals for most sales teams. Open and Click are useful for advanced reporting but can create noise if AEs aren't actively using that data.

For each enabled activity, choose how it's stored in Salesforce. The right choice depends on how your Salesforce team reads the activity feed.

A call placed with lemlist is logged in Salesforce as a Task with the subtype Call, carrying the call duration and the outcome. The activity is titled "Call done from [campaign name]", and calls placed outside a campaign sync too. The contact has to exist in Salesforce first — a call on a contact that isn't synced yet waits until it is.

The call outcome is written to the Task's Call Result field (CallDisposition). In the Calls row of the Activities tab you can type the exact value you want sent for each call status. If you leave it blank, lemlist sends the label of the call status as it reads in lemlist — a call marked No answer arrives as "No answer".

Four independent toggles control what lemlist sends alongside the call: Calls note, Calls recording, Calls transcript, Calls summary. They are on by default.

Everything enabled is written into the Task Description, always in the same order — the rep's note, the AI summary, the recording link, then the transcript. A section with nothing in it is skipped.

The Description fills up progressively. The Task is created as soon as the call ends with whatever exists at that moment, then rewritten when the transcript arrives, and rewritten again when the AI summary is generated.

A few things worth knowing before you turn these on:

An SDR team enables three activity types: Email Sent → Task, Reply Received → Task, Interested → Task. They skip Open and Click to keep the Salesforce activity feed clean. When an AE picks up a qualified lead, they see the full outreach history — email sent date, the reply, when the SDR marked them as interested — without leaving Salesforce or messaging the SDR.

Root cause: The activity type may be disabled, or there may be a permission issue on the Salesforce side.

Root cause: The value lemlist sends for the call outcome isn't one your Call Result field accepts. This happens when the field has been converted to a restricted picklist and the value typed in the Calls row — or the lemlist call status label used when that row is blank — doesn't match one of its options.

Root cause: Neither exists when the call ends — both are added on a later refresh. The call may also have no summary at all, or may have come from Aircall or Ringover rather than lemlist calling.

Root cause: lemlist rebuilds the Description on every refresh instead of merging it, so manual edits are replaced.

Root cause: This is a known limitation — only manual campaign unsubscribes sync. Bulk or direct unsubscribes added to the Unsubscribe section do not.