Mailshake

Run Mailshake cold outreach from your flows. Agents add recipients to campaigns, track leads flagged for follow-up, monitor opens, clicks, and replies, and list campaigns and senders to drive campaign-aware automations.

9 actions Basic auth available

Mailshake website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

The weekly prospect list lands from the research team with names, emails, and company fields

Each prospect is screened against the CRM for open opportunities, existing customers, and past opt-outs

List Campaigns resolves the right sequence for the segment, and List Senders confirms which sending account it runs on

The outbound lead reviews the screened list with merge fields rendered, prunes the entries that should not receive cold email, and approves the batch

Add Recipients enrolls the approved prospects with their personalization fields

List Replies runs on a schedule, and repliers are flagged with Create Lead and written to the CRM

The sales channel gets each new lead with the reply body attached, assigned for human follow-up

What This Integration Enables

Cold outreach runs on two assets that are easy to spend and slow to rebuild: sender reputation and prospect goodwill. Mailshake manages the sending; this connector puts the decisions around the sending under orchestration. FlowRunner agents enroll screened prospects into campaigns with personalization fields, poll opens, clicks, and replies on a schedule, flag repliers as leads with notes attached, and enumerate campaigns and senders so automations stay campaign-aware instead of hardcoded. The design conviction here is that the interesting automation in outbound is not the sending, which Mailshake already does, but the perimeter around it: what gets in, and what happens when a human being writes back. Both moments route through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline. - Sync prospects from CRMs, forms, and sheets into campaigns, screened before enrollment - Detect replies within the polling interval and convert them to flagged leads with notes - Feed opens and clicks into scoring, timing, and escalation logic - Keep automations portable across campaigns and senders via runtime lookup

Without FlowRunner

Lists pasted into campaigns Prospects move from research sheet to sequence by copy-paste, unscreened against the CRM

Replies buried in the tool A prospect answers on Tuesday and sales finds out at Friday's pipeline review

Engagement data unused Opens and clicks accumulate in dashboards nobody wires into follow-up decisions

With FlowRunner

Enrollment as a screened pipeline Every recipient passes CRM checks and a human review before entering a sequence

Replies become leads in minutes Agents poll for replies, flag leads, and route them to the owner with context

Activity drives the next step Opens and clicks feed scoring and timing logic instead of decorating a report

Use Case Scenarios

The screened enrollment pipeline

Research delivers 200 prospects to a [Google Sheets](/integrations/google-sheets) tab. The agent checks each against [HubSpot](/integrations/hubspot): open opportunities, current customers, and prior unsubscribes come off the list. The survivors go to the outbound lead as a reviewable batch with merge fields rendered so broken personalization is visible before it ships. On approval, Add Recipients enrolls them, and Mailshake's own dedupe and block-list checks provide the second net. Nobody mid-deal gets a cold email asking if they have heard of your product.

Reply to routed lead before the coffee cools

Every 15 minutes, List Replies runs across active campaigns. Each new reply is matched to its recipient, flagged with Create Lead and a note quoting the reply, and posted to [Slack](/integrations/slack) with the campaign and sender context. Out-of-office replies are filtered by the agent and skipped. The rep answers a warm human with the full thread in view, hours or days sooner than the weekly check would have surfaced it.

Engagement-scored follow-up

A nightly agent pulls List Opens and List Clicks per campaign, aggregates per recipient, and scores engagement: multiple opens plus a pricing-page click crosses the threshold. Recipients who cross it without replying are proposed to the rep as manual-touch candidates, logged with their event history. The rep decides who gets a personal note. The signal Mailshake was already collecting starts changing what happens next, instead of describing what already did.

Human-in-Loop Highlight

Add Recipients is the point of no return in this connector: once a prospect enters a sending sequence, the emails go out in a real salesperson's name from a real domain, and neither the send nor its effect on the recipient's opinion of your company can be recalled. The failure modes are all list-shaped: the export that included current customers, the merge field that renders as a raw column header, the segment scoped to the wrong campaign. So enrollment is the gated step. The agent assembles, screens against the CRM, renders the personalization for inspection, and waits; the outbound lead prunes and approves; only then does the batch enroll. Everything after that gate is fast by design: replies get flagged within the polling interval and routed to a human, because the other unrecallable thing in outbound is a warm prospect left waiting.

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

9 actions

Campaigns

List Campaigns Lists sending campaigns with ID, title, status, sender, and creation date, paginated by nextToken. The lookup that keeps workflows campaign-aware instead of hardcoded to one sequence.

Recipients

Add Recipients Adds one or more recipients to an existing campaign so they enter the sending sequence, each with an email address and optional name and merge fields. Skips recipients already present or on the campaign's block list. The write this page's human gate governs.
List Recipients Lists a campaign's recipients with email, name, merge fields, and current engagement state, paginated. The roster read behind audits and enrollment reconciliation.

Leads

List Leads Lists leads across campaigns, filterable by campaign and status: open, won, lost, ignored, or reopened. The pull that feeds CRM sync and pipeline reporting.
Create Lead Flags a recipient in a campaign as a lead for follow-up, with an optional note. Used when a reply, a click pattern, or a rep's judgment says this person deserves human attention.

Activity

List Opens Lists email open events with recipient, message, and timestamp, optionally scoped to a campaign. Raw material for engagement scoring.
List Clicks Lists link click events with recipient, clicked URL, message, and timestamp. The strongest pre-reply intent signal in the dataset.
List Replies Lists reply events with recipient, subject, body, and timestamp. The action that turns outreach from broadcast into conversation, polled on a schedule.

Senders

List Senders Lists the sending accounts connected to Mailshake with ID, email address, and display name. Used to confirm which identity a campaign sends under before recipients are added to it.

Frequently Asked Questions

What can FlowRunner do with Mailshake?

FlowRunner agents can run List Campaigns, Add Recipients, and List Recipients in Mailshake, plus 6 more actions.

Does connecting Mailshake to FlowRunner require OAuth?

No. Mailshake connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Mailshake trigger a FlowRunner workflow automatically?

Mailshake doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Mailshake

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us