SalesRobot for AI agents
SalesRobot automates LinkedIn outreach, running connection and messaging campaigns across prospect lists so sales teams can scale cold outreach without manual messaging. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in SalesRobot.
Add a prospect to a campaign
Enrolls a new LinkedIn prospect into an active outreach campaign along with its messaging sequence.
Check a prospect's sequence status
Looks up where a prospect sits in an outreach sequence before deciding on the next message.
Send a message only after review
Sends a LinkedIn message into a prospect's inbox thread only once a rep approves the draft.
10 SalesRobot actions, graded by risk.
Every SalesRobot action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- salesrobot.list_campaignsList Campaigns
- salesrobot.list_inbox_threadsList Inbox Threads
- salesrobot.list_linkedin_postsList LinkedIn Posts
- salesrobot.get_linkedin_profileGet LinkedIn Profile
- salesrobot.list_linkedin_accountsList LinkedIn Accounts
- salesrobot.list_campaign_prospectsList Campaign Prospects
- salesrobot.get_prospect_sequence_statusGet Prospect Sequence Status
write
3Create and change things. Allow, or ask the user first.
- salesrobot.send_messageSend Message
- salesrobot.update_prospectUpdate Prospect
- salesrobot.add_prospect_to_campaignAdd Prospect to Campaign
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
SalesRobot in three steps.
- 01Your users connect SalesRobotThey add their SalesRobot api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “send Message” can wait for the user to approve.
- 03Any agent can actYour agent calls SalesRobot through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('salesrobot', { read: 'allow', write: 'ask', // send_message destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How SalesRobot connects.
Users add their SalesRobot api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same SalesRobot connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use SalesRobot from any agent.
SalesRobot and Arc0, answered.
Can I use SalesRobot with Claude, ChatGPT or Cursor?
Yes. Connect SalesRobot to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the SalesRobot actions you allow.
How do users connect SalesRobot?
Users add their SalesRobot api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which SalesRobot actions can my agent take?
10 in total: 7 read, 3 write and 0 destructive, such as “send Message”. Your policies decide which of them each agent may call.
Can I make my agent read-only in SalesRobot?
Yes. Allow read actions and deny writes in the SalesRobot policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call SalesRobot too?
Yes. The same SalesRobot connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug SalesRobot into your agent.
Your users connect SalesRobot once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan