Troubleshoot Lofty CRM logging
Fix the most common reasons SAMI activity stops appearing in your connected Lofty CRM and re-establish reliable logging.
When the Lofty integration is connected, SAMI mirrors calls, texts, notes, tags, and answered-transfer assignments into Lofty automatically. If that activity stops showing up there, this article walks you through the usual causes and how to clear them.
Confirm the connection is still healthy
SAMI only mirrors activity while the integration status is Connected, so the status badge is the first thing to check.
Open the Lofty integration
Head to Settings → Integrations and open the Lofty connection.
Read the status and timestamps
A status of Error means the last mirror attempt failed. The "last used" and "last error" timestamps tell you whether logging was ever succeeding and when it broke.
Re-save your API key
Paste your Lofty API key again and save. A successful save flips the status back to Connected and clears the previous error so the next activity can sync.
Re-saving the key is also how you recover from an Error status. Every successful mirror marks the integration healthy again, and every failed one marks it as Error with a fresh error timestamp.
Why an activity gets skipped
Not every miss is a failure. SAMI looks up the Lofty lead by the contact's phone number before it writes anything. If no Lofty lead matches that number, the activity is skipped on purpose, not logged as an error.
- No matching lead. If the contact's phone number does not exist on a Lofty lead, there is nowhere to attach the activity, so SAMI skips it. Add or correct the number in Lofty, then trigger a new activity.
- The activity type is turned off. Each type — calls, texts, notes, tags, and answered-transfer assignment — has its own toggle. If one type is missing while others log fine, the matching toggle is off. Re-enable just that toggle on the integration.
- Not connected. If the integration is disconnected, nothing mirrors at all. Re-save the key to reconnect.
Because matching is by phone number, the fastest fix for a skipped activity is to confirm the contact in Contacts uses the same number that is on the Lofty lead.
Read provider failure reasons
When the lead exists and the toggle is on but Lofty still rejects the write, SAMI records a provider failure and sets the status to Error. The reason tells you what to do next.
- api error — Lofty refused the request. This usually points to an invalid or revoked API key. Generate a fresh key in Lofty and re-save it.
- network error — SAMI could not reach Lofty. This is typically transient; the next activity often succeeds on its own.
- timeout — Lofty was slow to respond. Like a network error, retry by sending another activity before changing anything.
- invalid response — Lofty returned something SAMI could not read. Re-save your key, and if it persists, confirm your Lofty plan still includes API access.
Mirror outcomes are stored on the integration itself: a success refreshes the "last used" time and keeps the status Connected, while a failure stamps the "last error" time and flips it to Error. After fixing the cause, trigger one more activity from the Inbox or a SAMI Bot call to confirm logging has recovered.
Related articles
Last updated 2026-06-21