M for Mercury
Book a demo Sign in Get started
Automation

Outreach that runs itself — and stops the moment someone replies.

Build the journey once. Mercury runs it across every sender you have, paces each action inside daily caps and working hours, and hands the conversation back to a human the second it turns into one.

See plans Book a demo
Journey · Q3 outbound3 senders · running
View profileWarms the account up before the invitation
Done
InvitationWith a note written from the research
Done
Wait 2 daysCounted in working hours only
Now
If acceptedOtherwise the person waits, untouched
Branch
MessageStops here the moment they reply
Queued

An illustration. The steps are real journey nodes; the states are examples.

What runs it

A worker, a pacer and a limiter

01 · Journeys

Steps you can drag

Profile view, invitation, message, wait and condition. Start from a template or build your own, and change it while the campaign is running.

02 · Pacing

Spread across your senders

Every action is laid out sequentially so no two land too close together on one account, inside the workspace's working hours and one clock.

03 · Limits

Caps per sender, per action

Invitations, messages and profile views each have their own daily cap, plus a rolling weekly invitation cap. Hitting one is the limiter working.

Journeys01 / 03

Sequences with judgment, not just a timer.

A journey is a set of real LinkedIn actions with conditions between them. A person who accepts moves on; a person who does not is left alone rather than messaged anyway. A reply ends the sequence for that person immediately — no follow-up ever lands on a live conversation.

  • One journey, many senders — Mercury decides which account does what.
  • Pause a campaign and its queue stops; resume and it picks up where it stopped.
  • Remove a sender mid-campaign and the people it had already contacted wait for it, rather than hearing from a stranger.
See plans Build the audience first
Campaign · Q3 outbound412 people
View profile Invite Wait 2 days Message
MV
Marta VidalReplied — journey stopped
Replied
DS
Dev ShahInvitation accepted, message queued
Step 4
TB
Tom ByrneInvitation pending — no follow-up sent
Waiting
Safety02 / 03

The limiter is the product.

Each sender has its own daily caps for invitations, messages and profile views, and a rolling seven-day invitation cap on top. Steps only run inside your working hours, on one clock, so nothing can catch up at 3 a.m. When LinkedIn refuses an action, that sender waits in amber with a plain-word reason — the lead is untouched and never shown as failed.

  • A sender is only ever Active, Inactive or Restricted — three words, no scores.
  • Acceptance is swept fairly across senders, and invitations older than 30 days retire.
  • Provider limits are recorded per sender and per action, the day they appear.
Book a demo
Priya Raman · today09:00–18:00
Invitations
14 / 20
Messages
33 / 60
Profile views
80 / 80
MonTueWedThuFriSatSun
JM
Jonas MeyerLinkedIn asked us to slow down — waiting until tomorrow
Wait
Beyond the app03 / 03

What happens next is automated too.

A reply lands in the unified inbox with a byline saying whether you or the journey sent the last message. A positive one is flagged, pushed to your CRM with the activity logged, and announced in Slack or in-app. Everything you can click, you can also call — on every plan.

  • Webhooks for replies, acceptances and campaign events, the moment they happen.
  • A CLI — npm i -g @mformercuryy/cli — for launching and reporting from a terminal.
  • An MCP server, so an AI agent runs outreach under exactly the same limits as a person.
See plans Read the API docs
Eventswebhook · live
01
invitation.acceptedMarta Vidal · Priya Raman
200
02
message.repliedPositive · pushed to HubSpot
200
03
campaign.completedQ2 outbound · 1,140 people
200
Unified inboxCRMSlack

See a journey run on your senders.

Thirty minutes, your account count, your list — and the pacing explained in plain words.

Schedule a demo See Lead Finder