Woodpecker
Sales OutreachLet AI agents run your cold outreach lists in Woodpecker. Agents add prospects to campaigns, update prospect data, stop follow-ups when a reply lands, and monitor campaign status.
What This Integration Enables
Cold outreach fails at the edges: the prospect who already replied, the customer who should never have been on the list, the opt-out that got honored a week late. Woodpecker executes sequences well; what it cannot know is everything the rest of your stack knows about who should not be in them. FlowRunner agents close that loop. They screen and enroll prospect batches, keep names, companies, snippets, and tags in sync with the system of record, stop follow-ups the moment a reply or opt-out lands anywhere, and read campaign statistics back into reporting. The connector's actions split cleanly by stakes, and FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) model follows that split: enrollment and deletion wait for a person, while stopping emails to someone who asked is the one thing agents do without asking. - Enroll leads from CRMs, forms, sheets, and prospecting tools into campaigns, after screening - Sync prospect details and tags with an external system of record - Stop follow-ups instantly when replies or opt-outs arrive through any channel - Run list hygiene sweeps that propose deletions instead of performing them - Post per-campaign sent, opened, and replied statistics where the team works
Without FlowRunner
With FlowRunner
Use Case Scenarios
Sourced leads that arrive pre-screened
An [Apollo](/integrations/apollo) search produces two hundred target contacts. The agent checks each against List Prospects, drops the eleven already in the database with Replied status, drops three that match customer domains, and formats the rest with #segment tags and personalization snippets. The campaign owner reviews the batch in [Slack](/integrations/slack) and strikes two names they recognize. Add Prospects to Campaign enrolls the remainder in one call. The list that starts sending is the list a human saw.
The opt-out honored in minutes, not days
A recipient replies "please remove me" to their work inbox, or checks the opt-out box on a [Typeform](/integrations/typeform). The agent matches the email and calls Stop Follow-ups immediately: no queue, no approval, no Thursday follow-up firing while the request waits. The prospect record stays in the database carrying its history, and a weekly digest lists everyone paused this way so the team sees the pattern, not just the incident.
The database that stops accumulating
Quarterly, the agent pages through List Prospects and builds the hygiene report: prospects with bounced status, prospects untouched across every campaign for a year, duplicates by domain. Each candidate comes with its status and campaign history attached. The ops lead marks what goes, and only then does Delete Prospects run against the approved IDs. The report also flags where deletion is the wrong call, and those records get Stop Follow-ups and a #do-not-contact tag instead, so the suppression knowledge survives.
Human-in-Loop Highlight
Delete Prospects has a trap built into its permanence: it does not just remove a person from campaigns, it erases the record that they were ever contacted, ever bounced, ever asked to be left alone. Delete an opted-out prospect and the next list import can re-enroll them with a clean slate, which turns a courtesy into a complaint. So FlowRunner agents never choose between stopping and deleting on their own. Hygiene sweeps present each candidate with its history, and a person decides: Delete Prospects for the records that should not exist, Stop Follow-ups plus a suppression tag for the people the database must remember to leave alone. The same discipline gates Add Prospects to Campaign, because bulk enrollment into a cold sequence is a spend of sender reputation that no retry can refund. Agents assemble and screen at machine speed; membership in the send list is a human call.
Agent Capabilities
7 actionsProspects
5- List Prospects Lists and searches prospects with filters by email or campaign and paging by limit and page. Returns contact details, snippets, tags, and current status per campaign. The lookup that precedes every update, stop, and delete, and the screen that keeps bad enrollments from being proposed at all.
- Add Prospects to Campaign Bulk-adds prospects to a campaign, enrolling them in its automated email sequence. Each prospect object requires an email; name, company, title, industry, phone, snippets, and tags are optional. With Update Existing enabled, prospects already in the database are updated with the supplied values instead of skipped. The commitment step this page's human gate reviews.
- Update Prospect Updates an existing prospect by numeric ID, changing only the fields supplied. The enrichment write that keeps Woodpecker consistent with the CRM without touching what it does not send.
- Stop Follow-ups Stops all further follow-up emails for the specified prospects across their campaigns without deleting them, identified by numeric IDs or email addresses. The one write in this connector that should run without waiting for anyone.
- Delete Prospects Permanently deletes prospects from the database, removing them from all campaigns, by IDs or emails. Cannot be undone, and reserved for human-approved hygiene and compliance decisions.
Campaigns
2- List Campaigns Lists all campaigns with ID, name, status (RUNNING, PAUSED, DRAFT, COMPLETED), and creation date. The routing check before enrollment and the snapshot behind portfolio reporting.
- Get Campaign Retrieves one campaign's full details: sending schedule, sequence steps, mailboxes, and aggregate sent, opened, and replied statistics. The feed behind daily performance digests.
Frequently Asked Questions
What can FlowRunner do with Woodpecker?
FlowRunner agents can run List Prospects, Add Prospects to Campaign, and Update Prospect in Woodpecker, plus 4 more actions.
Does connecting Woodpecker to FlowRunner require OAuth?
No. Woodpecker connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can Woodpecker trigger a FlowRunner workflow automatically?
Woodpecker doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Woodpecker
$100 in credits. No card required. Connect in minutes.