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.

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.

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.

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.

Salesforce enforces a daily API call limit. Every sync lemlist performs — creating a record, logging an activity, updating a field — counts against that limit. If lemlist hits the limit, syncs queue up and may be delayed until the next day.

Open the API Calls tab to view your daily limit and current usage.

If you're consistently reaching 80% or more of your daily limit, increase it before you hit the ceiling. It's easier to raise the limit proactively than to deal with queued syncs during a high-volume sending period.

Click Update limit and enter a higher value.

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.

Root cause: Usually a missing required field, a permission issue, or a data type mismatch between lemlist and Salesforce.

Root cause: Your daily API limit may be close to or at capacity, causing lemlist to queue syncs.

Root cause: The selected date range may not cover the right period, or no sync has triggered yet.