Sales infrastructure for agents.
Give your agent what a sales team has: accounts that reach people, audiences to work on, sequences that run safely and the replies that come back. One API, one MCP server, signed webhooks.
7-day free trial · card required · cancel anytime.
- Claude Code
- Claude Desktop
- Cursor
- n8n
- Any MCP client
- REST
Your agent
Decides who to reach and what to say.
- Claude Code
- Cursor
- Your own agent
Outvoy
Runs it on real accounts, safely, and reports back.
- REST API
- MCP
- Webhooks
- Senders2 active
- Audiences148 leads
- Sequences4 steps
- Preview146 eligible
- Inbox3 unread
- Eventslive
Limits · warm-up · preview · blocklist
Channels & data
Where your agent reaches buyers.
- LinkedInLive
- Data enrichmentNext
- Email sendingNext
- Mailbox warm-upNext
More channels later
- MCP toolsOne per API capability, full surface
- 59
- event typesOne stable shape, as a feed or a webhook
- 23
- step typesVisit, like a post, invite, message
- 4
- webhook attemptsSigned, retried over about 45 hours
- 8
The problem
Outreach tools were built for clicking, not for agents.
We ran our own LinkedIn outbound from Claude on a well-known outreach tool. Every pain had the same root: the product was made for a person in a UI, and the API came later.
What hurt
What Outvoy does instead
- 01
Sequences only exist in the UI
The agent could add leads, but a person had to build the campaign by hand.
Campaigns, steps, delays and senders are API calls and MCP tools.
- 02
Search is a separate product
The agent couldn't find people on its own.
Search LinkedIn with filters or a pasted URL, Sales Navigator included, and import the results.
- 03
No safe way to rehearse
One wrong call sent real invitations.
Preview renders every message for every lead first. Sandbox senders simulate LinkedIn end to end.
- 04
State is hidden
“Why hasn't this lead been invited?” had no answer.
Every lead says what happens next, when, and why.
- 05
Events arrive without content
One webhook per event type, and the reply text missing.
One event stream with a stable shape and the message text, as a cursor feed or signed webhooks.
How it works
From an empty workspace to replies, in four steps.
- 1
Connect a LinkedIn account
Through a hosted page that handles the password, 2FA and checkpoints. We never see your credentials. Or create a sandbox sender that simulates LinkedIn.
POST/v1/ senders/ connect-link - 2
Define the audience
Fill a list from LinkedIn search filters, a Sales Navigator URL, profile URLs or a CSV, or the people who engaged with a post.
POST/v1/ lists/ {id}/ imports - 3
Launch a campaign
Visit, like their latest post, invite with a note, then message, each with its own delay. Preview every rendered message before anything is sent.
POST/v1/ campaigns/ {id}/ preview - 4
Handle the replies
A reply stops the sequence. Read and answer it in the unified inbox, or let your agent pick it up from the events feed, a webhook or MCP.
GET/v1/ events? types=lead.replied
Product
Everything a sales team has, as primitives an agent can call.
Audiences, sequences, preview, inbox and events — the same objects in the console, the API and the MCP server.
Audiences
Your agent finds the people on its own.
Fill a list from a LinkedIn search with filters or a pasted Sales Navigator URL, from profile URLs or a CSV, or from the people who engaged with a post. Imports run in the background and report progress.
- Custom CSV columns are kept as fields
- A workspace blocklist keeps people and companies out
POST/Build a listSequences
The whole campaign is an API call.
Visit the profile, like their latest post, invite with a note, then message — each step with its own delay. Templates read any field, so an agent can write the line that matters for each lead.
- Always on: stop when they reply, never message someone who isn't connected
- Unaccepted invitations are withdrawn after the window you set
POST/Templates and variablesRehearse every message before one is sent.
Preview renders every step for every lead and lists every problem. Missing variables and notes over 300 characters are caught and never sent.
Every lead says what happens next, and why.
No hidden queues: each enrollment carries its next action, when it will run and the reason it is waiting, in plain English.
Inbox
Every reply lands in one place.
Every conversation with a lead, both directions, across all your senders. A reply stops that lead's sequence at once; you or your agent answer from the account that owns the thread.
- Read and answer through the conversations API or MCP
- Filter by unread and by sender
POST/Handle repliesSandbox senders
Simulated LinkedIn accounts on a fast clock. Invitations get accepted, some people reply — test the whole flow without touching LinkedIn.
Multi-sender campaigns
Give a campaign a pool of accounts. Leads are spread across them, each sender within its own limits and hours.
REST API + OpenAPI
Senders, lists, campaigns, enrollments, conversations and events. Idempotency keys on every write, cursor pagination everywhere.
Built for agents
Everything in the console is an API call and an MCP tool.
The console is built on the same public API your agent uses, so there is nothing a person can do that an agent can't. Tool descriptions state the rules up front, so the agent doesn't learn them by failing.
- 59 MCP tools over streamable HTTP, authenticated with an API key
- OpenAPI document and an llms.txt for agents that read docs
- Idempotency keys on every write, cursor pagination everywhere
- Launches and sends marked as destructive, so clients ask first
Add it to Claude Code
$ claude mcp add --transport http outvoy https://api.staging.getoutvoy.com/mcp …Events & webhooks
Your agent hears about it the moment it happens.
One event stream with a stable shape and the message text included. Read it as a cursor feed, or have it pushed to signed webhooks.
A cursor feed
GET /v1/events from any point, filtered by type. Replies carry what the person wrote.
Signed webhooks
HMAC-SHA256 signatures, retries with backoff and a delivery log of every attempt.
Account safety
Your LinkedIn account is the asset. Outvoy paces like a person.
Conservative defaults on every sender, enforced by the engine rather than left to the agent. Raise them up to hard ceilings; the console shows when a value is in a risky band.
- 20 invitations a day, 100 a week
- 50 messages and 60 profile visits a day by default.
- 14-day warm-up
- New accounts start at 30% of their limits.
- Human pacing
- One action at a time, 2–6 minutes apart, in working hours.
- Backs off on trouble
- A LinkedIn limit or a broken session pauses the sender and raises an event.
Channels & data
LinkedIn first. The rest of the stack is next.
New channels arrive on the same primitives — senders, audiences, sequences, inbox, events — so what your agent learns today keeps working.
- Live
LinkedIn
Invitations, messages, visits and likes from real accounts.
- Next
Data enrichment
Work email addresses for the people in your lists.
- Next
Email sending
Send from your own mailboxes, on the same sequences.
- Next
Mailbox warm-up
Mailboxes ramped up gradually before they send at volume.
Comparison
What changes when the API comes first.
| Capability | Outvoy | Typical outreach tools |
|---|---|---|
| Create campaigns via API | Yes | Partly |
| Define the sequence via API | Yes | UI only |
| Search LinkedIn via API | Yes | Rarely |
| MCP server | Yes, full surface | Rarely |
| Sandbox senders | Yes | No |
| Preview / dry run of every message | Yes | One sample at a time |
| Explainable lead state | Next action, time and reason | A status label |
| Events with message content | Yes | Often missing |
Pricing
Pay per LinkedIn account. Each one costs less.
$39 a month for your first LinkedIn account, less for every one after it. Everything else is included: the API, the MCP server, unlimited leads and campaigns, and your mailboxes' warm-up.
7-day free trial · card required · cancel anytime
- 1st account$39/month, includes the minimum
- 2nd to 5th$25/month, each
- 6th to 20th$15/month, each
- 21st to 100th$10/month, each
- 101st and up$7/month, each
$89a month · $29.67 per account on average
Yearly: 2 months free. More than 250 accounts? Talk to us.
- Unlimited leads and campaigns
- Your mailboxes, with warm-up, reputation and placement tests
- The full API, the MCP server and signed webhooks
- Unified inbox, events and blocklist
- 5 sandbox senders and 5 sandbox mailboxes
- Warm-up, limits and working hours on every account
FAQ
Questions people ask first.
How it works, what it costs, and what it does with your LinkedIn account.
Something else? A person on the team answers.
Talk to usIs it safe for my LinkedIn account?
Outvoy is built to behave like a careful person: 20 invitations a day and 100 a week by default, a 14-day warm-up for new accounts, one action at a time with 2–6 minutes between actions, and nothing outside working hours. A LinkedIn limit or a broken session pauses the sender automatically. That lowers the risk; it can't remove it. Automating LinkedIn is against LinkedIn's User Agreement, and you accept the risk of a restriction.
Does it need my LinkedIn password?
No. You connect an account through a hosted page run by our LinkedIn infrastructure provider. Your password, 2FA codes and security checkpoints are entered there; Outvoy never sees or stores them. You can disconnect the account at any time.
Does it work with Sales Navigator?
Yes. Paste a Sales Navigator or regular LinkedIn people search URL and Outvoy imports the results into a list. You can also search with structured filters (keywords, title, location, industry, current company and connection degree) through the API.
Can I bring my own agent?
Yes. Anything that speaks MCP over HTTP (Claude Code, Claude Desktop, Cursor, your own client) can use the MCP server with an API key. Anything that can make an HTTP request can use the REST API. There is no Outvoy-specific SDK to install.
What is a sandbox sender?
A simulated LinkedIn account. It searches a generated population, sends invitations that get accepted after a short delay, and receives replies from some people, on a compressed clock so a day passes in about a minute. It runs the same engine as a real sender, so you can test a whole campaign, webhooks included, without touching LinkedIn.
What happens when someone replies?
Their sequence stops right away, wherever it was. The reply shows up in the unified inbox and as a lead.replied event with the message text, in the events feed and on your webhooks. You or your agent can answer from the sender who owns the conversation.
Where is my data stored?
In the European Union. Outvoy's application and database are hosted in the EU, and LinkedIn sessions are handled by our provider in France. The company behind Outvoy is based in Spain. Details are in the privacy policy, the data processing agreement and the sub-processors page.
How much does it cost?
You pay per connected LinkedIn account: $39 a month for the first, $25 each for the 2nd to 5th, $15 for the 6th to 20th, $10 for the 21st to 100th and $7 after that. Three accounts are $89 a month, ten $214. Leads, campaigns, the API, the MCP server, webhooks, the inbox and your mailboxes' warm-up are included. Yearly, two months are free.
Can I cancel or get a refund?
Yes. Cancel anytime from Settings → Billing: cancel during the 7-day trial and you are never charged; cancel later and it stops at the end of the period you paid for. If the first charge after the trial surprised you, write to us within 72 hours: if you haven't used LinkedIn since the trial ended, we refund it in full.
How do I get help?
Chat with us from this site or from the console (Help & support in the sidebar), or write to support@getoutvoy.com. We aim to answer within one business day and resolve every issue within 14 days at most. Every plan gets the same support.
Can I try it before paying?
Yes. Every subscription starts with a 7-day free trial with 2 LinkedIn accounts: connect them, rehearse with sandbox senders and launch real campaigns. A card is required to start it; we email you 48 and 24 hours before the first charge, and it happens on day 8 unless you cancel. Before the trial you can already sign up, explore the console and connect your agent.
Start in the sandbox. Go live when it looks right.
Start your 7-day free trial, point your agent at the MCP server and rehearse a full campaign against a simulated LinkedIn in minutes.