Learning objective
By the end of this tutorial, you'll know how to use Logs and API Calls to verify sync activity, catch errors before they affect your sales team, and keep your Salesforce integration running reliably.
Why this matters
Sync errors are silent by default — a failed activity log or missed lead update won't alert you unless you check. By the time your sales team notices data gaps in Salesforce, multiple records may already be missing activity history. Regular monitoring means you catch issues early, fix them fast, and keep your CRM accurate.
Prerequisites
Your Salesforce integration is connected and configured in lemlist
You have lemlist admin access
Phase 1: Monitor sync activity with Logs
Step 1: Open the Logs tab
In the Salesforce integration, open the Logs tab. This is your primary tool for understanding what synced, what failed, and when. Get into the habit of checking it after any configuration change, or on a regular cadence — weekly works well for most teams.
Select a date range covering the period you want to review, then click Refresh.
Step 2: Read the log results
Each entry shows whether a sync succeeded or failed, which record was affected, and (for errors) the reason. Error entries typically name the field and cause — read them carefully before making changes. Common causes include permission issues, required fields with missing values, and field type mismatches.
Phase 2: Manage API usage
Step 3: See how many API calls lemlist uses
Salesforce gives each org a daily API call allowance, shared by every app connected to it. Every sync lemlist performs — creating a record, logging an activity, updating a field — counts against that allowance.
Open the API Calls tab. It splits usage in two sections:
Global Salesforce API calls usage: Used (24h) shows the calls used over the last 24 hours by all apps connected to your org. Total number of API calls available (24h) shows the total Salesforce allows for your org.
lemlist specific API calls usage: Used (24h) shows the calls lemlist sent over the last 24 hours. lemlist is permitted to use (24h) shows the custom limit lemlist is allowed to use.
Salesforce does not break its limit down per app, so lemlist counts its own calls. The lemlist number is an estimate, accurate to about ten minutes.
Step 4: Set the lemlist limit
Use the lemlist usage to set a limit that matches what lemlist really needs and keeps room for the other tools connected to your org.
In lemlist specific API calls usage, click Update limit, enter the new value, then click Update.
✅ Verify: the new value shows under lemlist is permitted to use (24h).
Step 5: Get notified when the limit is reached
Under Notification Preferences (Get notified when API limits are reached), enter one or more addresses in the Enter email addresses field. They receive an email when lemlist reaches its limit.
What happens when lemlist reaches its limit
When lemlist reaches its custom limit, the sync pauses. The sync resumes on its own, and you don't need to do anything for it to restart. Two messages tell you the sync is paused, each with a countdown.
On the API Calls tab: "lemlist has reached your custom API limit for the 24h rolling window. Sync resumes on its own in about 1 minute."
At the bottom of the lemlist window: "lemlist paused the Salesforce sync: it reached the API limit set for it over 24h. Activities are queued and lemlist retries in about 1 minute. No data is lost." This banner has a Raise the limit link and a Dismiss button.
A call blocked by the limit is not counted, so the lemlist Used (24h) number does not keep climbing while the sync is paused.
Practical example
A RevOps manager checks Logs every Monday as part of their weekly CRM hygiene routine. One week they spot a recurring error on a specific rep's activities. Reading the error message, they see the Salesforce user mapping is missing for a new hire. They add the mapping, and future syncs for that rep log correctly. Past records aren't updated retroactively, but no further data is lost.
Troubleshooting
Logs show errors on specific records
Root cause: Usually a missing required field, a permission issue, or a data type mismatch between lemlist and Salesforce.
Read the error message in the log — it typically names the field and the reason for failure
Check whether the Salesforce field is required and whether lemlist is sending a value for it
Confirm the connected Salesforce user has write permission on the relevant object
Sync is paused or delayed
Root cause: lemlist reached its own limit, or another app used up your org's Salesforce allowance.
Open the API Calls tab and compare the two sections
If lemlist Used (24h) has reached lemlist is permitted to use (24h), lemlist hit its limit. Wait for the countdown, or click Update limit to raise it
If lemlist is under its limit but the global Used (24h) has reached Total number of API calls available (24h), another app used up the org's allowance. Check the other tools connected to your Salesforce org
Consider disabling lower-priority activity types to reduce lemlist's API usage
Logs show no entries even though campaigns are running
Root cause: The selected date range may not cover the right period, or no sync has triggered yet.
Widen the date range and click Refresh
Confirm your campaigns are actively sending and not paused





