# Zapier integration

> Connect Reply to thousands of other apps with Zapier: the published triggers and actions, and the Zapier step you can place inside a running sequence.

**Reply publishes a Zapier app with a fixed catalogue of triggers and actions, connected with your API key. It also works the other way round: a Zapier step inside a sequence hands a contact to a Zap mid-flow, which no other integration does.**

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

## At a glance

| | |
| --- | --- |
| **Availability** | Available. Included on plans that offer the Zapier integration – check yours in Billing |
| **Direction** | Both, through separate mechanisms: events out of Reply, actions into Reply |
| **Sync timing** | Event-driven. Events are collected and dispatched continuously rather than on a sync cycle |
| **What you need** | A Zapier account and your Reply API key |
| **Surfaces** | **Setup:** in Zapier, with your Reply API key. **Note for agents:** an assistant connected over MCP can perform the same contact and sequence actions directly, without a Zap in between |
| **Does not** | Fire on anything outside the published event list · share Zaps between teammates · replace webhooks for high-volume or custom payloads |

## Availability

Available on plans that include the Zapier integration. You will also need a Zapier plan that covers the number of tasks you expect; that side is Zapier's, not Reply's.

## How to connect Zapier

### Before you start

- Copy your Reply API key from **Settings → API key**
- Decide whether you want Reply to *start* Zaps, to *receive* actions from them, or both

### Connect

1. In Zapier, create a Zap and search for **Reply**.
2. When asked to connect an account, paste your Reply API key.
3. Choose a trigger or an action.
4. Test the step in Zapier – it will pull a real recent record so you can confirm the connection.

## What to expect

### What Reply can start a Zap with

Events published as Zapier triggers include a new reply, an email opened, a link clicked, a bounce, an opt-out, an email sent, a contact finished, a reply being categorized in the inbox, a contact being updated, and a contact saved manually.

### What a Zap can do in Reply

Published actions include creating a contact, pushing a contact to a sequence, adding and pushing in one step, removing a contact from a sequence, moving a contact to the next step, marking a contact as replied, and finishing a contact.

### The Zapier step inside a sequence

This is what makes Zapier different from the other platforms here. You can add a **Zapier step** to a sequence, and when a contact reaches it Reply hands that contact to your Zap. The sequence carries on afterwards.

It is useful when a step in your outreach needs something Reply does not do (enrich from a source Reply has no integration with, create a record in a niche system, notify a channel) without leaving the sequence.

### What doesn't work this way

- **Anything outside the published lists.** The trigger and action catalogues are fixed. If the event you want is not there, use a [webhook](/troubleshooting/webhook-was-not-received/) instead.
- **Teammates' activity.** Zaps are connected with one person's API key and receive that person's scope. A colleague's replies do not reach your Zap.
- **High-volume or custom payloads.** Zapier is convenient, not the cheapest route at volume. Webhooks give you the full payload and no per-task cost.

## Common problems

- **The Zap never fires** – confirm the event is in the published list, and that the activity belongs to the API key's own scope rather than a teammate's.
- **A Zap fires twice** – check whether two Zaps are listening to the same event.
- **Actions fail on contacts that already exist** – use the add-and-push action rather than create, or handle the existing-contact case in the Zap.
- **A Zapier step in a sequence does nothing** – check the Zap is switched on in Zapier; a paused Zap accepts the handoff and drops it.

## Pause or disconnect

Turn a Zap off in Zapier to stop it without losing the configuration. Removing the Reply connection in Zapier disables every Zap that uses it. Regenerating your Reply API key has the same effect; every Zap connected with the old key stops.

## FAQ

### Which Reply events can start a Zap?

Replies, opens, clicks, bounces, opt-outs, emails sent, contacts finished, inbox categorization, contact updates and manual saves. Anything outside that list needs a webhook.

### Can a Zap add someone to a sequence?

Yes. There are actions for creating a contact, pushing an existing one, and doing both at once.

### What is a Zapier step in a sequence?

A step that hands the contact to your Zap mid-sequence, then carries on. It is the one thing this integration does that the others do not.

### Should I use Zapier or a webhook?

Zapier for convenience and for connecting to apps you do not want to write code for. Webhooks for volume, for the full event payload, or when the event is not in Zapier's list.

## Need help connecting Zapier?

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](https://support.reply.io/) 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.

## Related

- [CRM and integrations](/capabilities/integrations/) – everything Reply connects to
- [n8n integration](/integrations/n8n/) – the same idea, self-hosted
- [Why was a webhook not received?](/troubleshooting/webhook-was-not-received/) – the alternative at volume

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction) – everything a Zap does, done directly
- Webhooks: [Webhook events](https://docs.reply.io/api-reference/introduction) – the full event catalogue and payloads
- MCP: [docs.reply.io/mcp](https://docs.reply.io/mcp/overview) – for an AI assistant, a direct alternative to building a Zap