Watch the Full Build

If you've ever built outbound systems for yourself or clients, you know the "hard part" usually isn't writing copy. It's the glue work: getting leads into your outreach tool, qualifying them, keeping your CRM updated, routing positive replies to the right place, and making sure nothing falls through the cracks.

That's exactly why we're excited about this update: Victoria AI is now live on Zapier.

With a native Zapier connection, you can move data into Victoria (to run outbound on autopilot), and also move response data out of Victoria (to keep your CRM and internal workflows synced) — without CSV uploads, custom webhooks, or duct-tape automations.

In this post, I'll walk through the exact system we built in the demo: a two-Zap "automated sales engine" that qualifies leads, runs multi-channel outreach on LinkedIn + email, and routes positive replies into your CRM automatically.

The Core Idea: Victoria Runs Outbound, Zapier Runs the Plumbing

Think of Victoria as your outbound infrastructure.

Once a lead is added to a Victoria campaign, Victoria can:

  • scrape their LinkedIn and website for context,
  • generate custom variables (like icebreakers and pain points),
  • run a multi-step outbound sequence across LinkedIn + email,
  • and (optionally) handle replies using an AI autoresponder that can push toward booking a meeting.

Zapier's job is to make sure Victoria is always fed with the right leads, and that the rest of your business systems stay updated as conversations happen.

That's why the system in the video is split into two automations:

Zap #1: Leads IN → Outreach ON

Zap #2: Replies OUT → CRM + workflows

Zap #1: Automatically Qualify Leads and Add Them to a Victoria Campaign

This first automation is what eliminates the most annoying step in outbound: manually uploading lead lists.

In the demo, leads are stored in a Google Sheet. That sheet could be populated manually, but ideally it's fed by something upstream like Apollo exports, Clay, a scraper, or an enrichment pipeline. The key is that the sheet becomes your "staging area."

Then the Zap runs on a schedule (daily at midnight in the demo), pulls in leads, qualifies them, and only passes the "good ones" into Victoria.

Here's the flow:

You trigger the Zap on a schedule so it runs consistently in the background. From there, Zapier pulls in rows from Google Sheets — not just one lead, but a batch (10, 100, 1,000… whatever fits your workflow). This gives you a predictable routine: new leads come in, the system processes them, and the campaign stays fueled.

Next, the Zap qualifies each lead using AI research. In the demo, Perplexity is used to research the company and return a "qualified" or "disqualified" decision based on criteria like:

  • Are they B2B?
  • Do they likely do $1M+ in revenue?

Your criteria can be totally different — industry, headcount, tech stack, location, services, intent signals, whatever matters for your offer. The point is you're filtering out junk before it ever touches your outbound volume.

After that, the automation writes the qualification verdict back into the Google Sheet. This part is underrated. It keeps your lead database clean, prevents duplicate work later, and gives you a simple audit trail of what was accepted or rejected and when.

Finally, Zapier adds qualified leads directly to a Victoria campaign using the new Victoria AI Zapier action: "Add Lead to Campaign." You map fields like name, email, LinkedIn URL, company name, website, and any other metadata you want Victoria to reference in messaging.

Once the lead is inside Victoria, everything else happens automatically: research, personalization, sequencing, and outreach across LinkedIn + email.

At that point, you're no longer "running outbound." You're maintaining a machine that runs itself.

Why This Changes the Game: Personalization at Scale Without the Busywork

Most outbound tools either let you scale volume or they let you personalize well — but not both without a bunch of manual effort.

Victoria's approach is different: the lead enters the campaign, then Victoria automatically scrapes and builds a research profile, and then uses that profile to generate variables like:

  • a relevant icebreaker,
  • the likely pain point,
  • a tailored angle for your offer.

Those variables get injected into your multi-step sequence. So your messaging doesn't feel like spray-and-pray, even when you're running at scale across channels.

That's what makes the Zapier connection so powerful. Zapier removes the "lead loading" labor, and Victoria handles the "research + personalization + sequencing" labor.

Zap #2: When Prospects Reply, Push Everything Into Your CRM Automatically

Most people stop once they've automated lead intake. But the real value is on the back end: what happens when replies start coming in?

That's what the second Zap does.

Instead of manually monitoring inboxes and LinkedIn DMs, you can trigger an automation every time a lead responds inside Victoria. This trigger includes a surprisingly useful payload: the lead's details, what they said, sentiment, and even what your AI autoresponder replied back (if you have it enabled).

In the demo, that response data is sent into ClickUp as a new CRM task. But the same concept applies if you use HubSpot, Pipedrive, Airtable, Sheets, Salesforce, or anything else in Zapier's ecosystem.

Once it's in your CRM, you can do almost anything:

Route the lead to the right rep, notify the team in Slack, kick off a pre-call workflow, send a custom asset, update pipeline stages, or start a separate marketing nurture sequence. The trigger is the moment of intent — the reply — and Zapier lets you attach your company's operating system to that moment.

The Autoresponder Layer: Booking Meetings Without Touching the Keyboard

One of the coolest parts of the demo is how the Victoria autoresponder fits into the system.

When enabled, Victoria can automatically respond to inbound replies — positive, neutral, negative, or question-based — using rules, documents, and instructions you provide. In the video, the goal is set to book a meeting, and a calendar link is supplied so the autoresponder can push for scheduling when the prospect shows interest.

This is important: it doesn't mean you can't handle replies manually. You can. But if your goal is speed-to-lead and maximizing booked meetings, the autoresponder becomes a force multiplier. Zapier then ensures that as soon as the conversation moves, your CRM and your team move with it.

Putting It All Together: Your "Two-Zap Sales Engine"

By the end of the build, you have a clean system:

Leads get collected → qualified → added to an outbound campaign → messaged on LinkedIn + email → replies handled → meetings booked → CRM updated → internal workflows triggered.

And the best part is you don't have to constantly babysit it. Once it's running, your job shifts from "doing outbound" to "improving a machine."

That means you can spend your time where it actually matters: tightening your ICP, improving your offer, refining your sequence, testing angles, and improving qualification logic — not chasing CSVs and copy-pasting leads.

What You Can Build Next With This

Once Victoria is connected to Zapier, the door opens up to way more than the demo.

You can trigger outreach based on form submissions, webinar signups, new Stripe purchases, inbound leads that didn't convert, job posting signals, LinkedIn intent events, or leads added in your CRM. You can also build workflows around responses, like sending a personalized pre-call teardown, generating a proposal draft, enriching the lead further, or routing based on sentiment and topic.

The demo shows the foundation. The interesting part is what you stack on top.

If you want to watch the full build, check out the video here.

And if you want, tell me what your CRM is (ClickUp, HubSpot, Pipedrive, etc.) and where your leads live — I'll outline the cleanest version of these two Zaps for your exact stack.