# Install the Reply Chrome extension

> Add Reply's extension to Chrome, sign in with single sign-on, a password or an API key, and set the view mode so it is ready for prospecting on LinkedIn.

**Add the extension from the Chrome Web Store, where it is listed as Findy - Email Search and Outreach, then open it and sign in with the Reply account you already use. Single sign-on is the default route; email and password and API key sign-in are also offered. Keep a signed-in Gmail tab in the same browser profile, because email search runs through your own Google session.**

_Status: Reviewed – written against Reply's product documentation on 2026-09-22, not yet confirmed against the running product._

## Goal

A working copy of the [Chrome extension](/capabilities/chrome-extension/) in your browser,
signed in to your workspace, so that LinkedIn profiles, Gmail threads and your CRM records
can be turned into Reply [contacts](/specifications/contacts/) without leaving the page.

## Preconditions

Google Chrome or another Chromium browser; the extension is built and tested for Chrome,
and behavior elsewhere is not guaranteed. A Reply account: the extension comes with one,
and what you can do inside it follows your plan. Sign-in is refused while a subscription is
expired, canceled, blocked, suspended or under review, so settle the subscription state
first. Be signed in to Gmail in the same browser profile for the best search results.

## Steps

1. Open the Chrome Web Store and look for **Findy: Email Search and Outreach** – that is the store name of Reply's extension, and the same listing is what older articles call the Reply LinkedIn Email Finder. Click **Add to Chrome**, read the list of data the extension asks to reach, and confirm in the pop-up with **Add extension**.
2. Put the icon where you can reach it: click the puzzle-piece button at the top right of Chrome and choose **Pin** for the extension, so you can open it from the toolbar while you browse.
3. Click the icon to open the extension and start signing in. The default route hands you to Reply's sign-in page in a new tab; approve there and the tab closes on its own, returning you to the extension already signed in. If the email you approve has no Reply account behind it, one is created in the same pass and you continue straight into the extension.
4. To use a password instead, choose **Sign in with Email** on the sign-in screen and enter the address and password of your Reply account.
5. To use a key, click **Sign in with API key**. In a separate tab, open the Reply web app, go to **Settings** in the top header menu and find the **API key** section, copy the value from the **Your API Key** field, paste it into **Enter your API key** in the extension, and click **Sign in**. The button is offered on Reply's own build of the extension; branded builds distributed by a partner may hand sign-in to their own provider instead and hide it.
6. Open **Settings** inside the extension and pick how you want it to appear: **Plugin view** switches between the in-browser popup, a separate window and Chrome's side panel, and **Plugin position** decides which edge it opens against. Choose a separate window or the side panel if you intend to place calls; dialing is unavailable while the extension runs as a popup.
7. Leave a Gmail tab open and signed in to the same browser profile. Address checks run through that session, so the search side of the extension only becomes usable once Gmail is loaded at least once.

## Expected result

The extension opens on its own set of tabs (**Search**, **People**, **Tasks** and **CRM Sync**
) and the account you signed in with is shown inside it. Your Data Search allowance appears
as used against total; the total comes from your plan, not from a fixed number, so the value
you see is your own.

## Verification

Open any LinkedIn profile with the extension running. The person's name, title and company
should appear in the extension within a few seconds, which proves three things at once: the
content script is active on LinkedIn, the sign-in token is valid, and the extension is
talking to the right workspace. Then open the **People** tab: it should list contacts that
already exist in your Reply account.

## What happens next

With sign-in done, the next move is revealing addresses. See
[Find contacts on LinkedIn with the Chrome extension](/how-to/find-contacts-on-linkedin/).
Everything the extension saves lands in the same [contact](/specifications/contacts/)
records you work with in the web app, so nothing needs importing afterwards.

## Common mistakes

- Trying the extension in a browser that is not Chromium-based. It was designed for Chrome, and support cannot promise the rest.
- Signing in with an account whose billing has lapsed. The extension answers with "This Reply account has been deleted, locked out, or disabled." or "Your account has been suspended or expired.": both point at subscription state, not at the password. Reactivate under Plans & Billing in the web app, then sign in again.
- Skipping Gmail. Without a loaded Google session you get "Email search initialisation failed. Please open gmail in new browser tab or click here to fix." on the first search attempt.
- Waiting for an update prompt. Chrome updates Web Store installs by itself. The advice to remove and reinstall, and to leave the extracted folder where it is, belongs to builds downloaded from a Reply account rather than from the store.
- Staying in popup view and then wondering why the call buttons do nothing.

## Related

- [Chrome extension](/capabilities/chrome-extension/) · [Contacts](/specifications/contacts/)
- [Cannot sign in](/troubleshooting/cannot-sign-in/)
- [Configure account settings](/how-to/configure-account-settings/)
- [Find contacts on LinkedIn with the Chrome extension](/how-to/find-contacts-on-linkedin/)

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction) – the same API key you can sign in with also drives the REST endpoints
- MCP: [docs.reply.io/mcp](https://docs.reply.io/mcp/overview) – connect Reply to an AI client instead of a browser