Custom campaign or agents

Build agentic workflows and scheduled tasks using our MCP that run 24/7. Have an agent run your LinkedIn the way a great salesperson would, with a ton of context about you, your business, your ideal customer, your tone of voice and how you handle objections.

How it runs. Agent Builder designs your campaign; it doesn’t run it. You connect Claude, or your AI assistant, to Flow’s MCP, paste the campaign in, and your assistant runs it from there on a schedule. Everything it does on LinkedIn goes through Flow, inside your account’s safe limits.

Flow’s prebuilt campaign

Run a proven campaign in a click. It warms up leads and sends connection requests.

How it works →

Custom campaign or agents

Build agentic workflows and scheduled tasks using our MCP that run 24/7.

You’re reading this one

Why an agent, not a drag-and-drop sequence

Most LinkedIn tools give you a drag-and-drop campaign builder. You set fixed steps, every prospect gets the same sequence, and each step knows next to nothing about you or the person on the other end. It runs the workflow cleanly every time, and it can’t handle a curveball.

An agent works the way a great salesperson would. Before it acts, it reads the whole conversation and the lead’s profile, and it knows your tone of voice, your ideal customer, your offer and how you handle objections. So it can make judgement calls a fixed sequence can’t:

  • Leave someone alone when they’re not a fit, or when the conversation has already moved on.
  • Write every message for the person it’s going to, in your voice, rather than send a canned template.
  • Answer a reply in context, handling the objection the way you would.
  • Pass leads to the rest of your stack, such as HubSpot, Salesforce, Apollo or Instantly, in the same run.

And you stay in the loop. Start with an agent that drafts replies for you to approve, and hand over more once you trust what it writes.

Give it context on your business

Context is what makes an agent sound like you and pick the right people. In Agent Builder you attach it as skills, starting from Flow’s four templates: Tone of voice, Ideal customer profile, Offer and qualifying question and Handling replies and follow-ups. Fill them in with your own details, or write your own. There’s no limit on how much context you give it: every attached skill travels with the agent, in full.

Design it from set actions

Writing a workflow as one long prompt is painful, so Agent Builder lets you lay it out visually and writes the prompt for you. Every agent starts with a trigger, then the checks and actions you choose. A message can also carry its own Only send if conditions, so it only goes to the right people.

Triggers: what a run looks for

Someone accepts my request

Someone replies to me

Someone hasn’t replied for N days

Someone hasn’t accepted yet

Someone sent me a connection request

Go through every lead on the list

Find new people on LinkedIn

Something else, in your own words

Actions on LinkedIn

Send connection, with or without a note

Accept their request

Send message or InMail

View profile

React to or comment on a post

Custom action, in your own words

Checks

If connected

If connected in the last N days

If not yet messaged

If replied

If no reply for N days

Flow and your other tools

Add to, move to or remove from a list

Mark as Won or Lost

Mark conversation as read

Find their email

HubSpot, Salesforce, Apollo, Instantly or any tool your assistant is connected to

Agent Builder with the Send first message to connections template open: a Someone accepts my request trigger and a Send message step on the canvas, and the set actions listed on the right, with an arrow pointing to Send Connection with Note
Agent Builder. The set actions are on the right: click one to add it, or drag it onto the canvas.

Use cases to start from

Flow’s templates are ready-made use cases. Open one, make it yours, and copy it into your assistant:

  • Send first message to connections — a personal first DM to everyone who accepts, sent once.
  • Follow up after 1 week — one follow-up to connections who haven’t replied, and a drafted answer for you to approve for anyone who has.
  • Follow up after 1 month — one last useful message to anyone who’s still quiet.
  • Add new connections to your CRM — new connections go into HubSpot with their headline and company.
  • Enrich leads and add to email sequencer — leads who don’t accept get a work email from Apollo and go into an Instantly campaign.

Run it from your AI assistant

Three steps, all covered in detail in the Agent Builder guide:

  1. Connect Claude, or your AI assistant, to Flow’s MCP.
  2. Build your agent in Agent Builder, or press Run a Campaign → Design campaign on a list in Run Outreach to start one for that list.
  3. Copy it and paste it into your assistant. It sets up the scheduled task and runs it from then on.
The Agent Builder canvas with an arrow pointing to the Copy scheduled task button in its top-right corner
Copy scheduled task turns the whole agent, with its context, into one prompt for your assistant.
Claude’s Scheduled tasks screen with the New task button and example recurring tasks
Once pasted in, your agent lives in Claude as a scheduled task and runs on its own.

Because it runs in your assistant, you pause, edit or stop it there. If you change the agent in Agent Builder, copy it into your assistant again.

How Flow shows it

When your assistant has messaged or sent connection requests to leads on a list in the last 7 days, Flow shows that list as Campaign Running. In the Run a Campaign panel, the Custom campaign or agents card shows Running and when it was last active, such as Active 2 hours ago. Manage opens your agent in Agent Builder.

With Flow’s prebuilt campaign

The two work well on one list. Flow’s prebuilt campaign warms leads up and sends the connection requests, and your agent takes the conversation from there. If your agent sends connection requests too, it skips anyone who already has one waiting, and both draw from the same daily allowance.

⌘I