Apollo or ZoomInfo Extension Not Working on LinkedIn? A Clay and HubSpot Workflow Instead

If the Apollo or ZoomInfo Chrome extension stops working on LinkedIn, work through the vendor's own fixes first: reload the extension, sign out and back in, update it, then check your browser's cookie and site-data settings. If it keeps breaking, or your team is wary of LinkedIn's rules on browser add-ons, move the research step into a Clay table: build the list there, find and verify emails, and push only checked contacts into HubSpot.

Several r/sales threads this autumn describe the same thing: the extension sidebar won't load on profiles, prospecting stops for days, and reps ask what else to use. Here are Apollo's fixes and a workflow that doesn't depend on a sidebar.

Step 1: Apollo's own fix list

Apollo's troubleshooting article (updated 2 November 2026) gives this order, checking after each step:

1. Reload the extension. Extensions > ... beside Apollo.io > Reload Apollo Extension, then reload the LinkedIn page.
2. Reset your Apollo session. Sign out of Apollo and back in with the same account.
3. Update the extension. At chrome://extensions, turn on Developer mode and click Update.
4. Check the browser. Update Chrome, confirm the browser is supported (Apollo supports Chrome and Edge), allow Apollo third-party cookies, do a hard refresh, clear Apollo site data and check company-managed browser settings.
5. Rule out other extensions by turning them off one at a time.

One case isn't a fault: on Sales Navigator, Apollo says the extension "shows suggested leads on search pages, but bulk prospecting actions aren't supported". If a Sales Navigator profile shows nothing, open the standard LinkedIn profile.

ZoomInfo's extension has its own help pages; the same browser checks (cookies, site data, other extensions) apply.

Step 2: know the platform risk

LinkedIn's User Agreement (effective 3 November 2025), section 8.2, says you agree not to "develop, support or use software, devices, scripts, robots or any other means or processes (such as crawlers, browser plugins and add-ons or any other technology) to scrape or copy the Services, including profiles and other data from the Services". It also bans bots that "add or download contacts".

That doesn't make every sales extension a breach, but it means a workflow built on a LinkedIn sidebar can stop without warning. Building lists from a data provider instead of from the LinkedIn page itself avoids depending on it.

Step 3: a Clay table instead of a sidebar

1. Build the list in Clay. Start from a company or people search in Clay, or import accounts from HubSpot with a Lookup.
2. Find emails with a waterfall. Run providers in order and stop at the first result. Our post on enrich-then-verify order covers why verification comes after the find step.
3. Verify inside Clay. Add an HTTP API column that calls a verifier for each found email. Our Clay verification guide has the setup, including rate limits and a run condition so empty rows are skipped.
4. Route by result. Valid goes on, catch-all goes to a separate, slower campaign, invalid stops here. See catch-all leads in sequences.

If you'd rather work from a file, export the table (Actions > Export > Download CSV) and run it through the Clay table to email list tool, which reads the email and validation columns and merges repeats.

Step 4: push to HubSpot without duplicates

Clay University's HubSpot actions lesson separates Lookup actions, which "pull data FROM HubSpot INTO Clay without changing anything in your CRM", from Create and Update, which "are write operations that make real, permanent changes". Its advice: "The key with Create actions is ensuring you're not accidentally creating duplicate records", by combining them with Lookups.

In practice:

1. Lookup contact by email in HubSpot for each verified row.
2. Create only where the lookup found nothing and the verification result is valid.
3. Update existing contacts with conditions: only fill empty fields, or only write newer data. The lesson warns that without conditions "you could accidentally overwrite good data with incomplete or outdated information."
4. Write the verification result to a HubSpot property so sequences and lists can filter on it. Our post on re-importing verified emails into HubSpot covers the property and list setup.

Where SimpleVerifier fits

SimpleVerifier is the verification step: an HTTP API column in Clay, or a CSV upload at /verify. It doesn't find emails or replace the extension. The first 100 checks are free with a Google sign-in. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off, and one-time packs of 10,000 checks for $15 never expire (packs cover CSV verification, not the API). API calls are rate-limited, not unlimited; see pricing.