--- title: "Reply.io Integration" description: "Connect AI agents to Reply.io sales engagement. Agents add contacts and push them into campaigns, mark replies and finished sequences, and manage people and email accounts so outreach reacts to what prospects actually do." url: https://flowrunner.ai/integrations/reply-io date_modified: 2026-08-04T10:04:16-07:00 --- # Reply.io [Sales Outreach](https://flowrunner.ai/integrations/category/crm-sales) Connect AI agents to Reply.io sales engagement. Agents add contacts and push them into campaigns, mark replies and finished sequences, and manage people and email accounts so outreach reacts to what prospects actually do. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 13 actions · API key · available [Reply.io website](https://reply.io/) · [Platform Documentation](https://apidocs.reply.io/) · Capability data verified 2026-08-12 1. A prospect list arrives from the sourcing tool, scored and segmented 2. Get Person by Email screens each prospect against the existing database to catch people already in sequences 3. Create or Update Person syncs the new prospects' profiles: name, company, title, LinkedIn 4. The agent posts the enrollment plan: how many contacts, which campaign, which sending mailboxes carry it 5. The outbound lead reviews the batch and the target campaign, trims the edge cases, and approves 6. Add Contact and Push to Campaign enrolls the approved list, and the sequence starts sending 7. When a meeting gets booked, Mark Contact as Finished closes that prospect out before the next step fires ## What This Integration Enables Reply.io executes outreach sequences; the quality of what it executes depends entirely on what flows in and how fast the system reacts to what flows back. That is the job this connector does. FlowRunner agents create and update people, enroll them into campaigns, and, just as important, stop outreach the moment it should stop: marking contacts replied when the answer arrived somewhere else, marking them finished when the meeting is booked, and pulling them from one or all campaigns when circumstances change. The strongly held view here: in outbound, the expensive failure is not the email you did not send, it is the email you sent to someone who already answered. Every hour between a prospect's reply and the sequence noticing is a withdrawal from your domain's credibility. Agents close that gap because they never stop watching. - Enroll sourced prospects into campaigns with a review step before the first send - Stop sequences instantly on replies, bookings, and disqualifications from any connected system - Keep the people database synced with the CRM in both directions - Audit campaign stats and sending mailbox limits for deliverability planning ### Without FlowRunner **Enrollment is a CSV ritual**: Prospects wait in spreadsheets until someone imports them, and the hottest leads cool in the queue **Sequences email people who already answered**: A reply lands in the CRM or a meeting gets booked, and step four sends anyway **The people database rots**: Titles change, companies change, and Reply.io holds whatever was true at import time ### With FlowRunner **Sourcing flows into sequences**: Qualified prospects move from discovery to enrolled with one human approval in between **Outreach reacts to reality**: Replies, bookings, and disqualifications stop sequences the same hour they happen **Profiles stay synced**: The CRM and Reply.io agree on who a person is, because an agent reconciles them continuously ## Use Case Scenarios ### Sourced Tuesday, sequenced Tuesday A prospect search in [Apollo](https://flowrunner.ai/integrations/apollo) returns a fresh segment. The agent dedupes each against Reply.io with Get Person by Email, syncs profiles with Create or Update Person, and stages the batch for the campaign chosen from List Campaigns. The outbound lead approves the enrollment plan in [Slack](https://flowrunner.ai/integrations/slack), and Add Contact and Push to Campaign starts the sequence the same day the prospects were found, while the research that qualified them is still current. ### The sequence that stops the moment the meeting books A prospect books through [Calendly](https://flowrunner.ai/integrations/calendly). Within the minute, the agent calls Mark Contact as Finished, and the follow-up scheduled for tomorrow morning never sends. The same reflex covers replies that land in the CRM instead of Reply.io: Mark Contact as Replied pauses automation across campaigns. Nobody opens a "just bumping this" email two days after booking a demo, which is exactly the mistake prospects remember. ### The weekly deliverability and pipeline audit Every Monday, the agent pulls List Campaigns for per-campaign delivery and engagement counters, and List Email Accounts for each mailbox's daily sending limit. Both land in [Google Sheets](https://flowrunner.ai/integrations/google-sheets): reply and bounce trends per campaign, capacity headroom per mailbox. When a campaign's bounce rate climbs or a mailbox nears its limit, the alert reaches the channel before deliverability damage compounds, not after the domain is already warming its way back. ## Human-in-Loop Highlight Add Contact and Push to Campaign is where this connector stops organizing data and starts sending email to strangers in your company's name. The first sequence step lands in a real inbox and cannot be recalled, and a bad batch, wrong segment, stale titles, a campaign meant for a different persona, spends two things at once: the prospects themselves, who rarely give a second first impression, and your domain's sender reputation, which every future campaign inherits. So enrollment in FlowRunner is always a staged act: the agent assembles the batch, dedupes it, names the campaign and the mailboxes that will carry the volume, and a person approves before the push executes. Delete Person sits behind the same gate for the opposite reason: it permanently erases the record and its history, and the correct move is almost always Remove Contact from All Campaigns, which stops the outreach and keeps the memory. Agents feed and halt the machine. A human decides who the machine speaks to. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 13 actions ### Campaigns 2 - **List Campaigns** Retrieves all campaigns with id, name, status, and per-campaign delivery and engagement counters: people, delivered, opened, replied, bounced. The stats source and campaign picker. - **Get Campaign** Retrieves a single campaign by numeric id, including schedule, step sequence, and aggregate statistics. Used to verify what a sequence actually does before enrolling anyone into it. ### Enrollment 4 - **Add Contact and Push to Campaign** Creates or updates a person and enrolls them into a campaign in one call. The primary way outreach starts, and the action this page's human gate governs. - **Push Contact to Campaign** Enrolls an existing person by email into a campaign without touching profile fields. Used when the contact already exists and only the sequence needs starting. - **Remove Contact from Campaign** Removes a person from one campaign, stopping further scheduled steps there while leaving their other campaigns running. - **Remove Contact from All Campaigns** Removes a person from every campaign they belong to, halting all scheduled outreach while keeping the record. The correct off switch in almost every case. ### Contact Status 2 - **Mark Contact as Replied** Marks a person as replied, pausing automated steps and updating their status. The action that reflects replies received outside Reply.io. - **Mark Contact as Finished** Marks a person as finished, completing their sequence journey so no further steps send. The close-out for booked meetings and completed journeys. ### People 4 - **List People** Retrieves contacts with id, email, name, company, and status, paged to walk large databases. The scan behind sync and hygiene flows. - **Get Person by Email** Retrieves one person's full profile by email: name, company, title, location, phone, LinkedIn, notes, and status. The dedupe check before any enrollment. - **Create or Update Person** Creates a person or updates the existing one matched on email, setting profile fields without enrolling in any campaign. The sync primitive between CRM and outreach. - **Delete Person** Permanently deletes a person from the database and all campaigns. Cannot be undone, and gated accordingly. ### Email Accounts 1 - **List Email Accounts** Retrieves the configured sending mailboxes with address, sender name, and daily sending limits. The capacity audit behind deliverability planning. ## Frequently Asked Questions ### What can FlowRunner do with Reply.io? FlowRunner agents can run List Campaigns, Get Campaign, and Add Contact and Push to Campaign in Reply.io, plus 10 more actions. ### Does connecting Reply.io to FlowRunner require OAuth? No. Reply.io connects to FlowRunner with an API key, no OAuth flow required. ### Can Reply.io trigger a FlowRunner workflow automatically? Reply.io doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Reply.io?** This integration exposes Reply.io to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/reply-io. Site index: https://flowrunner.ai/llms.txt