Scenario: your GTM stack already has the pieces — prospecting tool, CRM, email. Connect them through Claude + Via and they become a warm outbound prioritization machine: every ICP-fit company gets scored by warm path, then routed automatically — warm-first to AEs with intro drafts to your connectors, cold-only into a sequence.
Apollo
HubSpot
Gmail
FindTopConnectionPaths (batch)
Result 25 with a usable warm path · 23 cold-only
Install once, paste the prompt, schedule the whole pipeline weekly.
In Claude, open Settings → Connectors → Browse connectors and add the four you'll need for this workflow. Via is currently in private beta, so you'll need to request access before it shows up in your directory.
Multi-tool workflows like this run more reliably in Claude Cowork than in regular chat. The agentic workspace handles the sequential connectors without losing context, and gives you an audit trail when something downstream breaks (an Apollo contact failed to enroll, a HubSpot field mapped wrong, a Gmail draft hit the wrong address) so you can see exactly where.
Replace [define ICP] with your target company filters (e.g. "Series B SaaS companies headquartered in NYC, 50–500 employees") and [define persona] with the titles you want to reach (e.g. "VP Engineering, Head of Engineering, CTO"). Claude pulls in batches of 25, dedupes against HubSpot, scores warm paths through Via, pushes warm-first companies to HubSpot with a Gmail draft to each connector, and finds Apollo contacts at cold-only companies to enroll in an Apollo sequence — one prompt.
Heads up: this prompt assumes you've already created an Apollo email sequence named "Q2 cold-only" — the prompt enrolls cold contacts into it but does not create the sequence for you. Set one up in Apollo with the cadence and copy you want before running this.
One prompt produces two things to review:
This is a lot of integrated pieces — pull → dedupe → score → route → draft → enroll across four MCPs — and at scale, parts will fail: Apollo's people search drops a contact, a Gmail OAuth blips, a sequence rejects a duplicate. In Cowork, every failure is a manual retry. Move to Claude Code and the prompt lives in a repo alongside your other GTM scripts, runs on a weekly schedule, retries failures with real error handling, and leaves a full audit trail when something downstream breaks. It's also where layering in timing, intent, and event signals on top of warm paths stops feeling brittle. Explore warm-outbound signals →
Via MCP is currently in private beta. We're onboarding teams running multi-tool GTM motions in Claude or ChatGPT.