Overview

In short

What does Reply integrate with?

Reply has native two-way sync with four CRMs, published apps for Zapier and n8n, two visitor-identification sources, and a public API plus webhooks for everything else. Connecting a mailbox or a LinkedIn account is account setup rather than an integration and lives under How to.

What Reply integrates with

IntegrationKindDirectionAvailability
HubSpotCRMTwo-way contacts and companies · Reply → HubSpot activityAvailable
SalesforceCRMTwo-way leads and contacts · Reply → Salesforce activityAvailable
PipedriveCRMTwo-way people · Reply → Pipedrive via triggersAvailable
CopperCRMTwo-way leads and people. No activityAvailable
ZapierWorkflow platformBoth, event-drivenAvailable
n8nWorkflow platformBoth, event-drivenAvailable
Website VisitorsData sourceYour site → ReplyAI SDR plans, existing trackers, or an add-on
RB2BData sourceRB2B → ReplyAvailable

Also connected, without a page of their own

  • Make – connects through Reply's public API. Follow Make's own Reply documentation; everything it does is available through the API.
  • Clay: two separate paths. For syncing data, set it up on the Clay side using Reply's public API and follow Clay's own documentation. Clay is also one of the tools the in-product assistant can connect to. See the section below.
  • Vidyard – video in email steps. Confirm current availability in the product before relying on it.

Tools the in-product assistant can connect to

Separately from the integrations above, Reply's in-product AI assistant can be connected to a catalogue of third-party tools so it can read and act in them on your behalf. Project trackers, several CRMs and a number of data providers are in that catalogue, and not every entry in it is available yet.

This is a different thing from an integration on this page, and it is worth being clear which one you want:

What you want to doWhere to go
Keep contacts and activity in step between Reply and another system, on a scheduleAn integration on this page
Ask the assistant questions about another tool, or have it act there while it worksThe assistant's connectors

A few tools appear in both places; Pipedrive and Clay among them. They are not the same connection and they do not share settings.

Setting up and managing the assistant's connectors is documented separately, at agents.reply.io.

Not integrations

Three things people look for here belong elsewhere, because they are account setup rather than connections between products:

What you wantWhere it lives
Connect a mailbox – Gmail, Outlook, Microsoft 365, or any provider over SMTP and IMAPConnect a mailbox
Connect a LinkedIn account, including Sales NavigatorConnect LinkedIn
Email warm-upWhy is warm-up not running?

Building your own

Where there is no native integration, there are three routes, in increasing order of effort:

RouteGood for
Zapier or n8nConnecting to an app without writing code
WebhooksReacting to Reply events at volume, with the full payload
REST APIAnything else – the complete surface

An AI assistant can also work in your account directly through Reply's MCP server.

How CRM sync works

The mechanics are the same for every CRM: steps, directions, field mappings, filters and manual syncs. They are covered once, in Sync Reply with a CRM, rather than repeated on each page. Each integration page covers only what is specific to that tool.

Three things are true of every CRM integration and worth knowing before you choose one:

  • Contacts travel both ways. Activity does not. Emails, calls and tasks go from Reply to the CRM, never back.
  • Activity records are written once and are not updated afterwards.
  • No CRM syncs deals or opportunities as objects. Some can create or move them through triggers.

Common problems

Need help connecting an integration?

If the connection fails or data isn't syncing the way you expect, the Reply support team can check your integration settings with you. Open the Reply Help Center and send the team a message.

To get an answer faster, include:

  • which integration and which sync step is affected
  • what you expected to sync, and what happened instead
  • the error text from the integration's Logs, or a screenshot of it

Don't send passwords, API keys, or access tokens.

Build with Reply