ManyReach
Sales OutreachRun cold email outreach with ManyReach, covering campaigns and sequences, the prospect CRM, mailing lists, sending mailboxes, tags, and blacklists. Agents keep sender health and suppression lists intact as volume grows.
What This Integration Enables
ManyReach treats the sending infrastructure as the thing worth modelling carefully, and the connector inherits that. A sender is not just an address: it carries its account type, whether custom SMTP, Gmail SMTP or OAuth, Microsoft OAuth or SendGrid, its daily limit, its warm-up limit with any progressive ramp settings, its tracking domain, and, when something has broken, the reason it is disconnected. Suppression is equally concrete, split into an address blacklist and a domain blacklist, with prospects who match either marked with a Blacklisted sending status rather than silently skipped. Deliverability validation runs as a batch with per-address verdicts of Valid, Invalid, Catch-All, Disposable or Unknown. In cold email the asset at risk is not an account, it is a domain and the reputation attached to it, and this is a connector built by people who know that.
FlowRunner agents drive the whole thing through connectors. They create and configure campaigns with daily volume controls and a sending schedule, and read the conditional sequence branches that fire on opened, not opened, replied and not replied. They manage the prospect CRM with custom personalization fields, reconstruct a prospect's full message history, and send a threaded reply from the mailbox that owns the conversation. The judgment FlowRunner adds sits at the one moment that cannot be walked back, which is the moment a sequence starts sending from a mailbox that was not ready.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Pre-flight before Start Campaign
Nothing in the connector prevents a campaign from starting on a mailbox that is mid warm-up or disconnected. So the flow does. Before Start Campaign is called, the agent walks List Senders filtered to the campaign's mailboxes, reads each one's warm-up state, daily limit and disconnection reason, and reads Get Sending Credits so a run does not stall halfway with prospects marked Insufficient Credit. Anything abnormal is reported with the mailbox named. A campaign either launches on healthy infrastructure or does not launch, and either way somebody knows why.
Validation as an enrolment gate
A sourced list arrives from an enrichment provider. Rather than trusting it, the agent calls Validate Emails with the raw addresses, polls Get Validation Batch until the run finishes, and reads the per-address verdict. Valid addresses go into a mailing list with Bulk Add Prospects using Add Only If New so existing records are not duplicated, and Not In Other Campaign so nobody is worked by two sequences at once. Invalid and disposable addresses are dropped with a reason. Catch-all results are the genuinely ambiguous case and are reported to a person rather than being decided by a default, because whether to send to catch-all domains is a risk posture, not a data rule.
Turning a reply into a recorded outcome
A positive reply arrives. The agent reads the exchange with Get Prospect Messages so the full context is available, drafts a response, and once a person has approved it delivers it with Send Reply threaded into the same conversation the prospect sees. It then records the outcome with Update Prospect, setting the sending status to Interested or Meeting Booked, tags the record with Add Prospect Tag, and writes the same outcome to HubSpot. Reporting stays accurate without anyone doing inbox triage twice.
Human-in-Loop Highlight
Start Campaign is a one-way door with a shared blast radius. The moment it fires, a sequence begins sending from real mailboxes on a real domain, and the cost of getting it wrong is not a failed run, it is a domain reputation that took months to build and cannot be rolled back by pausing the campaign afterwards. The specific failure this connector makes visible is a mailbox that is still in warm-up, or one that List Senders reports as disconnected with a reason attached, or one missing its tracking domain. An agent can see all three. It should not be the thing that decides to proceed anyway. So the pre-flight ends in a question to the person who owns the domain: "Campaign 'Q3 Manufacturing' is ready. 2 of 5 mailboxes are still in warm-up with daily limits of 12 and 15. 1,840 prospects validated, 96 invalid removed, 31 suppressed by blacklist. Start on the 3 warmed mailboxes, start on all 5, or hold until warm-up completes?" That is the digital andon cord placed where the irreversible act actually is: not at the reply, not at the list, but at the send.
Agent Capabilities
36 actionsAccount
2- Get Account Returns the account behind the configured key with its identity and plan-level settings. Useful as a connection smoke test before a longer automation.
- Get Sending Credits Returns the sending credit balance. Check it before launching a large campaign, because prospects whose send fails for lack of credit are marked with the Insufficient Credit sending status rather than being retried silently.
Campaigns
11- List Campaigns Returns a page of campaigns with status, sending identity, subject and body template, tracking flags, daily limits and schedule. Archived campaigns are hidden unless explicitly included, and cursor paging is available for large accounts.
- Create Campaign Creates a campaign with its initial email, sending identity, tracking behaviour and daily volume controls. Only the name is mandatory, and the campaign is created in Draft, so it must be started explicitly.
- Get Campaign Retrieves one campaign with its full configuration: status, sending identities, subject and body, CC and BCC lists, tracking settings, daily limit rules including progressive ramp-up, and the sending schedule with timezone and active days.
- Update Campaign Applies a partial update, so a single setting such as the daily limit or the subject line can change without restating the rest of the configuration.
- Start Campaign Starts a campaign so it begins sending within its schedule and daily limits, moving through Preparing into Running. Prospects already marked stopped, unsubscribed or blacklisted are not contacted.
- Pause Campaign Pauses a running campaign. Queued sends stop immediately and prospects hold their position, resuming from the same step when the campaign starts again.
- Archive Campaign Archives a campaign, stopping sending and hiding it from the default listing. A campaign that is still running must be archived with Confirm enabled, which is a deliberate friction worth preserving in a flow.
- Unarchive Campaign Restores an archived campaign to Draft so it reappears in the listing and can be reconfigured and started again.
- Delete Campaign Permanently deletes a campaign, its sequence and its statistics. Prospects remain in the CRM and in their lists, but the campaign history cannot be recovered, so prefer archiving when the record matters.
- Get Campaign Stats Returns sends, opens, clicks, replies, bounces and unsubscribes, optionally restricted to a date range. Enabling Refresh recomputes the figures instead of serving the cached snapshot, at the cost of a slower response.
- Get Campaign Sequences Returns the conditional sequence branches attached to a campaign. Each holds follow-up emails triggered by prospect behaviour, covering opened, not opened, replied, not replied and the interest-level variants, together with the operator and repeat count that decide when a prospect enters that branch.
Prospects
8- List Prospects Returns a page of prospects with contact details, company data, custom personalization fields, sending status and validation status. Narrow by exact email, by sending or validation status, by tags, by free text, and by including or excluding specific campaigns and mailing lists.
- Create Prospect Creates a single prospect. Email is the only required field and acts as the duplicate key, with an existing address rejected rather than merged. When no mailing list is given the prospect is filed into the Unassigned list, which is created on demand.
- Bulk Add Prospects Imports many prospects in one call and optionally files them into a mailing list or enrols them in a campaign. Add Only If New skips addresses already in the CRM, and Not In Other Campaign skips prospects currently being worked elsewhere, which together make this the safest bulk path.
- Get Prospect Retrieves one prospect with the complete stored record: contact and company fields, every custom personalization slot, list membership, sending status and whether sending is currently active.
- Update Prospect Applies a partial update. Setting the sending status is how an outcome from an external system gets recorded, for example marking a prospect Interested, Meeting Booked or Not Interested after a call.
- Delete Prospect Permanently removes a prospect and its list memberships. Message history already sent is retained in the campaign record, but the prospect will no longer be contacted.
- Get Prospect Messages Returns the full message history for one prospect, every email sent and every reply received, with subject, body, open and click counts and per-link click detail. Used to reconstruct a conversation before a follow-up.
- Add Prospect Tag Attaches an existing tag to a prospect. Tags are the main way to segment the CRM for later filtering and for building targeted campaign audiences.
Mailing Lists
3- List Mailing Lists Returns a page of mailing lists with id, title, folder and creation date. Lists group prospects for import and for feeding campaigns.
- Create Mailing List Creates an empty mailing list and returns its id, ready for import or for moving prospects into.
- Delete Mailing List Deletes a mailing list. The prospects it held remain in the CRM but lose this membership, so campaigns fed from the list stop drawing new prospects from it.
Senders
2- List Senders Returns the sending mailboxes with account type, daily and warm-up limits, tracking domain, signature and connection health including any disconnection reason. Filter by folder, status, warm-up state or a text search. This is the pre-flight check that decides whether a campaign should start at all.
- Get Sender Retrieves one mailbox with its full configuration and health: account type, daily and warm-up limits with any progressive ramp settings, tracking domain, signature, and whether it is currently disconnected together with the reason.
Messages
2- List Messages Returns sent messages, received replies or manually sent messages, filtered by campaign, follow-up step, sender, confirmed outcome status, address and subject. Each message carries its body, open and click counts and per-link click detail.
- Send Reply Sends a reply to a received message. Threading keeps it in the same conversation the prospect sees, while disabling threading sends a fresh email instead. The sending address and reply-to can be overridden and additional recipients added.
Tags
2- List Tags Returns the tags on the account with id, title, description and type. Tags are scoped to campaigns, CRM prospects or senders, and the type filter narrows to one family.
- Create Tag Creates a tag scoped to campaigns, prospects or senders, so a flow can apply consistent segmentation without relying on tags being defined by hand first.
Suppression and Validation
6- List Blacklisted Emails Returns the individual addresses on the account blacklist. Blacklisted addresses are never contacted by any campaign, and matching prospects are marked with the Blacklisted sending status.
- Add Emails To Blacklist Adds addresses to the account blacklist so no campaign contacts them again. This is how an opt-out captured outside ManyReach becomes enforceable inside it.
- List Blacklisted Domains Returns the domains on the account blacklist. Domain-level suppression is the right level for competitors, existing customers and organizations that have asked not to be contacted.
- Add Domains To Blacklist Adds domains to the account blacklist, suppressing every address beneath each of them across all campaigns.
- Validate Emails Submits raw addresses, existing prospect ids, or both for deliverability validation and returns a batch id. Validation is asynchronous, so poll for the result rather than assuming it completes inline.
- Get Validation Batch Returns the progress and per-address verdict of a submitted batch, reporting Valid, Invalid, Catch-All, Disposable or Unknown once processing has finished.
Frequently Asked Questions
What can FlowRunner do with ManyReach?
FlowRunner agents can run Get Account, Get Sending Credits, and List Campaigns in ManyReach, plus 33 more actions.
Does connecting ManyReach to FlowRunner require OAuth?
No. ManyReach connects to FlowRunner with an API key, no OAuth flow required.
Can ManyReach trigger a FlowRunner workflow automatically?
ManyReach doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with ManyReach
$100 in credits. No card required. Connect in minutes.