> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/integrations/crm/finding-activities-in-your-crm.md). # Finding Mobly activities in your CRM When Mobly captures an interaction with a lead — a scan, a logged call, a sent email, a Pulse sequence send — it tries to write that as an activity record on the lead's CRM record. This article covers **what gets logged, where to find it per CRM, and what doesn't sync.** ## What Mobly logs as a CRM activity The following Mobly actions create an activity record in your CRM (for CRMs that support activity logging — see the per-CRM table below): * **Lead scanned** at an event — logged with the event name and timestamp * **Engagement action from the mobile app** — call, text, email, social outreach, calendar booking * **Send Content** (a file shared from the mobile app) * **Note added** to the lead — each note syncs as its own activity record * **Pulse sequence email sent** — automated sends from Pulse sequences The lead's **Description** and **Tags** don't create activity records — those are stored as fields on the lead record itself. ## Which CRMs support activity logging Different CRMs handle activity logging differently. Today: | CRM | Activity logging | Where you'll find Mobly activities | | -------------- | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **HubSpot** | ✓ Yes — as **Engagements** | Open the Contact → Activities tab. Mobly engagements appear inline with email opens, calls, and notes you've logged manually. | | **Salesforce** | ✓ Yes — as **Tasks** | Open the Lead or Contact → Activity Timeline. Mobly creates Task records with the activity type, subject, and timestamp. | | **Zoho** | ✓ Yes — as **Notes** | Open the Lead or Contact → Notes tab. Mobly activities appear as Notes with structured content. | | **Pipedrive** | — No | Pipedrive doesn't support Mobly activity logging. Activities stay in Mobly's activity log only; field-level updates (last touch timestamp, etc.) still flow through normally. | | **Marketo** | — No | Marketo doesn't support Mobly activity logging. Field-level updates still flow through normally. | | **Pardot** | — No | Pardot doesn't support Mobly activity logging. Field-level updates still flow through normally. | For the full feature matrix across all CRMs, see the [CRM comparison](/help-center/integrations/crm/comparison.md). ## Where each Mobly action lands | Mobly action | HubSpot | Salesforce | Zoho | | -------------------- | -------------------------------------------------- | -------------------------------- | -------------------------------- | | Lead scanned | Engagement: "Scanned at \[event]" | Task: "Scanned at \[event]" | Note: "Scanned at \[event]" | | Call logged | Engagement (Call) | Task (Call) | Note | | Email sent / logged | Engagement (Email) | Task (Email) | Note | | Text sent / logged | Engagement (SMS) | Task (SMS) | Note | | Note added in Mobly | Engagement (Note) | Task (Note) | Note | | Calendar booking | Engagement (Meeting) | Task (Meeting) | Note | | Send Content | Engagement (Email/SMS) — content reference in body | Task — content reference in body | Note — content reference in body | | Pulse sequence email | Engagement (Email) | Task (Email) | Note | For Pipedrive, Marketo, and Pardot, none of these create CRM activity records. ## I expected an activity but I don't see it — what to check 1. **Confirm your CRM supports activity logging** (table above). Pipedrive, Marketo, and Pardot don't — and that's expected behavior, not a bug. 2. **Check Mobly's Reconciliation tab** for the lead. If the sync to your CRM failed (auth issue, field validation, missing required field), the activity may not have been written. See [Reconciliation](/help-center/integrations/crm/reconciliation.md). 3. **Confirm the lead synced first.** Mobly only writes activities to a CRM record that exists. If the lead itself didn't sync (still queued for enrichment, blocked at Reconciliation), the activities are still in Mobly waiting. 4. **Check timing.** Activity sync isn't instant. Most activities land in your CRM within a few minutes; sequences batch on the send schedule. 5. **Still missing?** Send your CSM the Mobly lead ID + the time you took the action + which CRM you're checking. They can trace the sync history. ## Related articles * [Comparing the CRM integrations](/help-center/integrations/crm/comparison.md) — full feature matrix * [How data flows from Mobly to your CRM](/help-center/integrations/crm/how-data-flows.md) * [Reconciliation](/help-center/integrations/crm/reconciliation.md) — what to do when sync fails * [Tracking missing leads](/help-center/the-hub/working-with-leads/tracking-missing-leads.md) — for the lead-side of the same question --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.getmobly.com/help-center/integrations/crm/finding-activities-in-your-crm.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.