Claude for sales teams: the connectors and the Sales plugin

The sales connectors available today

A connector lets Claude read from, and in some cases write to, another tool under the signed-in person’s own account. These are the four that matter most for a sales development team, each built by the vendor itself and listed in Claude’s connector directory:

The Outreach connector’s listed tools are lookups. It gives Claude the context of what is in Outreach: who is in which sequence, what was said in a meeting, which emails went out. The Apollo connector is the one that acts, because it can enrich a contact and put them into a sequence.

Anthropic’s Sales plugin

The connectors give Claude access. The Sales plugin gives it routines. Anthropic publishes it on GitHub, and it runs in Cowork, Anthropic’s desktop app, and in Claude Code. Its 36 skills fall into five groups:

• Your day. A daily briefing, call prep, call summaries with a follow-up draft, an inbox sweep, scheduling, activity logging, and end-of-day and end-of-week wraps.
• Accounts and prospecting. Account research against your ICP, an account brief from CRM, email and call data, stakeholder maps, outreach drafting, lead triage, lead routing and account tiering.
• Deals. Deal reviews, what is missing to move a stage, slip alerts, close plans, objection handling, competitive plays and opportunity updates.
• Pipeline and forecast. Pipeline health, a read-only CRM hygiene check, forecast narratives, team pipeline by rep, 1:1 prep and win/loss patterns.
• Customers. Health checks, attributed customer quotes from calls and email, and upcoming renewals.

It works with HubSpot, Salesforce and Close as the CRM, Gmail or Outlook for email and calendar, Gong, Fireflies, Zoom or Otter for calls, Clay, ZoomInfo, Apollo, Lusha or Crunchbase for data, and Slack or Teams. Every skill also works with nothing connected, using exports and files you upload.

What an SDR’s day looks like with it

The useful way to judge this is against the work an SDR repeats every day. With HubSpot, Apollo and a mailbox connected:

• Morning. The daily briefing lists the day’s meetings with account context and the replies waiting.
• Research. Account research pulls company news and checks fit against the ICP, and the Apollo connector finds and enriches the right contacts.
• Outreach. Draft outreach writes the sequence, and Apollo adds the contacts to it.
• After a call. The call summary drafts the follow-up email and proposes the CRM updates, and the rep approves them.

None of those steps is new. What changes is that they happen in one conversation instead of across five tools, and the logging happens while the call is fresh instead of at the end of the day. Post-call logging is the step that decays first in most SDR teams, so that alone is a real gain in CRM accuracy.

Follow-up is where this pays most. At ConvertCart, fixing follow-up and the meeting confirmation flow cut no-shows from 44% to 15%. A drafted follow-up and a booked invite minutes after the call make that discipline easier to keep, but only if someone owns sending them. The full fix is in how to reduce meeting no-shows.

What it does not do

Every skill above runs on two inputs it cannot create: a definition of who is worth contacting, and a definition of what counts as qualified. Lead triage scores against your ICP, so a vague ICP produces confident scores of the wrong accounts. Give it criteria a rep could check. For WorkStore, inbound leads were qualified on four: budget, genuine need, timeline and the number of units required. Deal review grades opportunities on your stage definitions, so if “discovery” means different things to different reps, the review inherits it.

At Locus, where Shobhit ran global SDR and revenue operations, MQL to SQL conversion went from 10% to 25% with no extra leads and no new tooling. The change was a written definition of qualified, enforced when a lead moved stage. The sales qualification framework sets out how to write one, and the ICP framework covers the targeting side.

Access is the other thing to plan. Each connector signs in as the individual, so Claude sees exactly what that person’s permissions allow. An over-broad CRM role is now over-broad in a much faster interface. Check roles before rollout, not after.

Where to start, by stack

HubSpot teams connect HubSpot first. It is the only connector here with full read and write across the CRM, and it pairs with the Sales plugin’s logging and pipeline skills. HubSpot’s own agent is covered in the HubSpot Prospecting Agent.

Salesforce teams on Sales Cloud enterprise edition go through Salesforce in Claude, which is an admin project rather than a per-rep toggle.

Apollo users add the Apollo connector for research and sequencing. Apollo’s own scheduled agents are covered in Apollo’s AI agents.

Outreach teams add the Outreach connector for context: meeting history and sequence status alongside the CRM. Whether a team needs Outreach at all is in Outreach vs Salesloft.

The broader point is the one in AI is a layer, not another tool: the gain comes from Claude working across the tools you already pay for, not from adding another tool beside them.

References

• Sales plugin. Anthropic, knowledge-work-plugins on GitHub. Skills, supported connectors, installation.
• HubSpot connector. Claude connector directory. Built by HubSpot, added November 2025, 36 tools.
• Apollo connector. Claude connector directory. Built by Apollo.io, added February 2026, 13 tools.
• Outreach connector. Claude connector directory. Built by Outreach, added February 2026, 15 tools.
• Salesforce in Claude. Anthropic, 15 September 2026. All accessed 2 October 2026.