Loading tutorials…
Loading tutorials…
Loom sends without CRM context are just emails with extra steps. With the integration done right, every video logs as an activity, view tracking flows to the contact record, and reps stop tab-switching between Loom and CRM. Here's the full setup.
Who this is forRevenue leaders or RevOps people running Loom across a sales team that already uses HubSpot, Salesforce, Apollo, Outreach, or Salesloft. If reps are recording Looms but not logging activities, this fixes that gap.
What you'll need
Step 1
HubSpot, Salesforce, Outreach, Salesloft, Apollo, Gong: all have native Loom integrations. Confirm yours is supported before configuring.
Open Loom Settings → Integrations. Browse the available list.
Native integrations as of 2026: HubSpot (Sales Hub + Service Hub), Salesforce (Sales Cloud + Service Cloud), Outreach, Salesloft, Apollo, Gong, Chorus, Pipedrive, Front, Intercom, Zendesk.
For unsupported CRMs (Close, Copper, etc.): use Zapier as a bridge. Loom → Zapier → CRM. Less rich than native (no per-send tracking) but workable.
For Gmail-only workflows: use Loom's Chrome extension. It logs activities to whatever CRM has a Gmail sidebar (most CRMs do).
Decision: pick the ONE primary CRM integration and configure deeply. Multi-CRM setups create attribution confusion — keep it simple.
Step 2
Loom Settings → Integrations → HubSpot → Connect. Authorize. Map fields. Test with a sample contact.
Settings → Integrations → HubSpot → Connect.
OAuth into HubSpot. Approve the requested scopes: contact read, contact write, activity write, deal read.
After auth, map the Loom activity to a HubSpot timeline event. Default: "Loom video sent" activity type. Customize the icon and color in HubSpot Settings → Integrations → Loom.
In HubSpot, install the Loom Chrome extension for HubSpot users. The record button appears inside HubSpot Email composer, Sequences, and the Help Desk.
Test: open a contact record in HubSpot → Send Email → click the Loom record button → record a 30-second test → send. Verify the activity appears on the contact timeline within 30 seconds.
Verify view tracking: open the Loom in a different browser session. Within 60 seconds, the contact timeline updates with "Loom watched 100%."
Step 3
AppExchange → Loom for Salesforce → Install. Configure custom objects. Add Loom component to Contact / Lead / Opportunity page layouts.
Salesforce admin → Setup → AppExchange → search "Loom" → Install Loom for Salesforce (managed package).
Install for All Users (or specific profiles if you need to limit access).
After install, Salesforce creates a "Loom Video" custom object linked to Contacts, Leads, Accounts, Opportunities.
Add the Loom component to your page layouts: Setup → Object Manager → Contact / Lead / Opportunity → Page Layouts → drag "Loom Activity" component to the right side.
In Loom: Settings → Integrations → Salesforce → Connect (OAuth). Approve scopes.
Test: open a Contact in Salesforce → click the Loom component → record a test video → confirm it logs as an activity. Open the recorded Loom in another session → confirm view tracking flows back.
For Lightning Email: the Loom record button auto-appears in the email composer once the package is installed.
Step 4
Loom → Integrations → Outreach (or Salesloft) → Connect. Authenticate. Configure step types. Looms become a step type in sequences.
Settings → Integrations → Outreach → Connect. (Same flow for Salesloft.)
OAuth into the platform. Approve scopes: prospects read/write, sequences read/write, activities write.
In Outreach: Settings → Customize → Step Types → enable Loom as a step type. Now sequence builders can drop a "Send Loom" step into any sequence.
Configure auto-fill: when a rep adds a Loom step to a sequence, Outreach auto-populates the prospect's name in the email template. Personalization variables flow into the Loom thumbnail + caption.
Test: build a 3-step sequence with a Loom step at #2. Enroll a test prospect. Verify the Loom step renders correctly when it fires, with a unique per-prospect tracking link.
Salesloft pattern is identical; both platforms now natively support Loom as a first-class step.
Step 5
Apollo Settings → Integrations → Loom → Connect. Install Loom Chrome extension for inline recording inside Apollo email composer.
In Apollo, Settings → Integrations → Loom → Connect.
OAuth into Loom. Approve scopes.
Install the Loom Chrome extension (loom.com/chrome-extension) if not already installed.
In Apollo email composer, the Loom record button now appears alongside Insert Image / Insert Link.
Click record → record screen + face → click Insert. Apollo embeds the Loom thumbnail with a tracking link.
When the prospect watches, Apollo logs a "Loom watched X%" engagement event on the contact. Reps see this in the Apollo activity feed.
For Apollo Dialer + Voicemail Drop: pair Loom video with voicemail drops for multi-touch async sequences. Common 5-touch pattern: text email → Loom on touch 2 → voicemail drop on touch 3 → text email on touch 4 → final Loom on touch 5.
Step 6
In CRM, build dashboards: Looms sent per rep, view rate, avg watch %, Loom-to-meeting conversion. Pipe data to Looker / Tableau / native reports.
In HubSpot: Reports → Sales Analytics → custom report on "Loom sent" activity type. Group by owner. Add view rate and avg watch % as columns.
In Salesforce: build a report on the Loom Video custom object. Fields: Owner, Send Date, Total Views, Avg Watch %, Linked Opportunity.
In Outreach/Salesloft: native step-type analytics show Loom send rate, open rate, watch %, reply rate per sequence step.
Build a single revenue-team dashboard combining: Looms sent, watch rate, meetings booked from Looms, deals influenced by Loom touches.
Track weekly cadence: target 5-10 Looms/week per BDR, 2-4 demo recaps/week per AE. Reps below those numbers are leaving leverage on the table.
A/B test framework: split reps into two groups. Group A uses Looms on touch 2 of cold sequences; Group B uses text only. Measure reply rate + meeting conversion at 30 days.
Step 7
Train reps to record INSIDE the CRM (using the integration buttons), not the Loom app. Audit weekly: % of Looms with linked contact.
Behavior shift: when a rep records for a specific prospect, they should click the Loom button INSIDE the CRM email composer — not open the Loom Desktop app, record, then copy-paste the link.
Why: recording inside the CRM auto-links the video to the contact and auto-creates the activity. Recording in the Loom app and pasting the link means manual logging that nobody actually does.
Audit: weekly, pull the % of Loom sends that have a linked CRM contact. Healthy target: 90%+. Below 70%, reps are recording outside the integration.
Reinforcement: 1:1 nudge with reps below target. Often they don't realize the integration is faster.
Run a 30-min team training showing the difference: timed comparison of "record inside CRM" vs "record + copy-paste." The CRM-integrated flow saves 30-45 seconds per Loom.
Common mistakes
Recording in the Loom app and copy-pasting links
What goes wrong: Activity logging fails. View tracking doesn't flow to the contact. CRM reports show 80% under-counted Loom usage. Reps can't measure what's working.
How to avoid: Force the in-CRM recording path. Train reps explicitly. Audit weekly. The integration only delivers ROI when used as designed.
Connecting multiple CRM integrations
What goes wrong: Same Loom logs to HubSpot AND Salesforce. View events double-count. Attribution becomes unreliable. Dashboards show inflated numbers.
How to avoid: Pick ONE primary CRM integration. Disable secondary ones. If you genuinely use 2 CRMs (e.g., sales in Salesforce, support in Zendesk), scope the Loom integration to specific folders.
Skipping Salesforce permission set assignment
What goes wrong: Reps install Loom for Salesforce but can't see the buttons. They blame the integration, abandon it, and revert to copy-paste. Setup is wasted.
How to avoid: Setup → Permission Sets → Loom User → assign to every user who should record. Verify by opening Salesforce as a non-admin user and confirming the buttons appear.
No view-tracking notifications
What goes wrong: Reps don't know when prospects watch. They miss the warm-engagement window where follow-up converts. Looms become send-and-forget.
How to avoid: Loom Settings → Notifications → enable Slack or email alerts on "First external view." Reps follow up within 5 minutes of a view — 3-5x reply rate vs day-late follow-up.
Not tracking attribution
What goes wrong: Loom-influenced deals get attributed to other touches because nobody tags the influence properly. Sales leaders can't justify the Loom spend at renewal.
How to avoid: Build attribution into your CRM: when a deal closes, the rep tags Loom in the "touchpoints" multi-select field. Quarterly review: what % of closed-won had a Loom in the journey?
Generic per-prospect message
What goes wrong: Integration sends 'Hey {{first_name}}' Looms with no real personalization beyond the merge field. Prospects sense the template and don't engage.
How to avoid: Use the integration to AUTOMATE the logging, not the personalization. Reps still record per-prospect. The integration handles the activity create + link tracking, not the creative.
Recap
Done — what's next
How to set up Loom for personalized sales outreach
Read the next tutorial
Hand it off
Connecting the integration is a 90-min project per CRM. Owning the rollout — training, auditing, building dashboards, optimizing per-rep behavior — is ongoing. A vetted video editor + RevOps partner on EverestX can run this from $14-16/hr — typically $500-1,200/mo depending on team size.
See video editor rates
Yes, the HubSpot integration works on Free, Starter, Professional, and Enterprise. Loom-side requires Business plan. Activity logging works across all HubSpot tiers; advanced features like sequence step-types require HubSpot Sales Hub Pro or Enterprise.
Yes via Zapier (or Make / n8n). Loom → Zapier → your CRM. Less rich than native: no per-send unique tracking link, no in-CRM record button. Workable but adds friction. For Close, Copper, Pipedrive, etc.
When a Loom link is forwarded and a new person watches, Loom logs them as 'Anonymous viewer' (since they didn't come from the original CRM-linked send). The original contact still gets the watch event for the first viewing. To track forwards explicitly, use Loom's 'Require email to view' setting (Enterprise).
Yes — when Loom is sent as a step in an Outreach or Salesloft sequence, it counts as one outbound email touch. Loom video is the email content, not a replacement for the email itself. Plan sequence cadence accordingly.
The CRM activity remains as a historical record but the embedded link becomes broken. Prospects clicking the link see a 'Video not available' page. For compliance/audit: don't delete sent Looms — archive instead. For mistakes: delete the activity AND the video to clean up fully.
Loom
Most reps record Looms that look like screenshares from 2018. The reps closing 2-3× more in async video did the same setup work — backdrop, CTA card, thumbnail strategy, CRM logging. Here's the full sales-outreach configuration.
Loom
Loom is the easiest async-video tool to install — and the easiest to misconfigure if you skip the workspace + defaults step. This walks through the full first-time setup so you don't end up with 200 untitled videos scattered across 6 personal accounts.
Loom
Loom AI turns a 10-minute recording into a 4-line summary, 6 chapter markers, and a list of action items in 30 seconds. The features are powerful but only useful when configured for your team's workflow. Here's the full setup.
Loom
Most teams hit the DIY Loom ceiling at 100-200 videos. Quality plateaus, library decays, and the founder/team lead stops being able to maintain it. Here's the honest framework for when to bring in a video editor — and what the role actually does.
Descript
The best content marketing teams produce one long-form piece and extract 5-10 short-form pieces from it. Descript is built for this workflow — transcript-driven highlight extraction, auto vertical cropping, captions on every clip. Here's the playbook.