Resources · Make integration

Woodpecker Make integrationAutomate Woodpecker with Make.

What if every reply, click or bounce in your cold email campaigns updated the rest of your stack on its own? The Woodpecker Make integration offers 18 modules, including 12 instant triggers. This guide shows sales and growth teams how to connect an account and build a first scenario.

Try the Woodpecker integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Woodpecker Make integration let you automate?

The Woodpecker Make integration links your Woodpecker account to Make, a no-code tool where you chain apps into a scenario, the automation you build. Woodpecker tells Make the moment a prospect opens, clicks, replies or bounces, and Make can also create, update, search or delete prospects for you.

Replies land where your sales team works. Watch Prospect Reply fires as soon as a prospect answers or gets moved to Replied by hand. Pass that prospect to your CRM or your team chat, and nobody has to scan the Woodpecker inbox to spot a hot lead.

New leads join a campaign without a CSV. When a form, a spreadsheet or another app produces a new contact, Create a Prospect adds it to Woodpecker, then Add Prospects to a Campaign places it in the right sequence. An agency feeding several client campaigns saves the export and import round trip.

Your lists stay clean. Watch Prospect Bounced, Watch Prospect Invalid and Watch Prospect Blacklisted each warn Make about a dead or unsubscribed address, so you can flag the same contact in the tools that still hold it.

The listed modules only cover prospects and campaign membership. For anything else in the Woodpecker API, Make an API Call reuses the same connection. Many apps also have a node in n8n, another automation tool; the n8n vs Make comparison sets out the criteria. To budget your runs, read Make pricing, and if you would rather learn the editor properly, Make training starts from zero.

Connect

How do you connect Woodpecker to Make?

  1. 01

    Generate your API key in Woodpecker

    In Woodpecker, open Settings, then the API Key tab, and click Generate API Key. Copy the key shown on screen. You need an active Woodpecker account for this, since Make signs in with that key.

  2. 02

    Add a Woodpecker module and create the connection

    In your Make scenario, add any Woodpecker module and click Create a connection. A connection is your Woodpecker account linked to Make once, then reused by every Woodpecker module. The Connection name field is optional; a clear name helps if you manage several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then save. Make can now read your prospects and campaigns, and the next Woodpecker module you add picks this connection from the list.

First scenario

Your first scenario: turn a new lead into a Woodpecker prospect

GoalWhen a new contact appears in another app, Make creates the prospect in Woodpecker and adds it to a campaign.

  1. 01

    Create the scenario and pick the source

    From the Scenarios page, create a new scenario and click the +. Choose the app where your leads arrive first, a form tool or a spreadsheet for example, and its module that watches new entries.

  2. 02

    Add Create a Prospect

    Click the + on the right of that first module, search for Woodpecker and pick Create a Prospect. Select your Woodpecker connection, or create it with your API key.

  3. 03

    Map the lead's details

    Fill the module fields by mapping data from the first module: drag its email, name or company into the matching boxes. Each bundle, meaning each lead that flows through, becomes one prospect.

  4. 04

    Send the prospect to a campaign

    Add Add Prospects to a Campaign after it. Once the connection exists, Make lists your campaigns, so pick the one this lead belongs in and map the prospect from the previous module.

  5. 05

    Test with Run once

    Create a test entry in the source app, then click Run once. Open the bubbles on each module to read the bundles it received, and check in Woodpecker that the prospect sits in the campaign.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each run uses operations, one per module per bundle, which is what Make counts on your plan.

Triggers

Which Woodpecker events can start a scenario?

12 modules start a scenario when something happens in Woodpecker. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Woodpecker as soon as it happens.

Woodpecker1Watch Email Opened

Watch Email Opened

Instant trigger

In Make“Triggers when a prospect opens your email (for the first time).”

You learn which prospect has just looked at your message, the first time they open it, so interest shows up outside Woodpecker. A later reopening of the same email does not start the scenario again.

How it fires
instant, Woodpecker calls Make through a webhook as soon as the open happens.
When to use it
to log first opens next to the contact in your CRM, so a rep calling the account sees that the email was read.
Watch out
an open says the email was displayed, not that the prospect cares; keep it as a signal, not as a reason to call.
Woodpecker2Watch Email Sent

Watch Email Sent

Instant trigger

In Make“Triggers when Woodpecker sends email to particular prospect .”

Every time Woodpecker sends an email to a prospect, Make receives that prospect, which gives you a complete sending log in the tool of your choice.

How it fires
instant, Woodpecker notifies Make by webhook right after the send.
When to use it
to record outreach activity in a CRM timeline, so account owners know a prospect is already in a sequence before they write to them.
Watch out
this trigger runs on every single send, so on a busy account it burns operations quickly; filter early in the scenario.
Woodpecker3Watch Follow-Up After Autoreply

Watch Follow-Up After Autoreply

Instant trigger

In Make“Triggers when you get an auto-reply and you set a date to resume follow-ups.”

This trigger tells Make that a prospect sent an automatic reply and that you set a date to resume the follow-ups. You get the prospect back in your scenario with the pause already decided.

How it fires
instant, the webhook reaches Make as soon as that resume date is set.
When to use it
to create a reminder task for the account owner, so a prospect on leave is not forgotten when the sequence restarts.
Watch out
it only fires once someone sets a resume date; a plain autoreply with no date goes through Watch Prospect Autoreplied instead.
Woodpecker4Watch Link Clicked

Watch Link Clicked

Instant trigger

In Make“Triggers when a prospect clicks on a link in your email.”

You find out which prospect clicked a link inside your email, a stronger sign of intent than an open. Make receives the prospect so you can act while the interest is fresh.

How it fires
instant, Woodpecker pings Make by webhook when the click happens.
When to use it
when your email points to a demo booking page or a pricing page and a click deserves a quick personal follow-up from sales.
Watch out
if several links sit in the same email, add a filter after the trigger so only the clicks you care about go further.
Woodpecker5Watch Prospect Autoreplied

Watch Prospect Autoreplied

Instant trigger

In Make“Triggers when an auto-reply is detected by Woodpecker or if you manually change a prospect’s status to ‘Autoreplied’.”

Make hears about every out-of-office or automatic answer, whether Woodpecker detected it or someone switched the prospect to Autoreplied by hand. That keeps absent contacts visible to the rest of the team.

How it fires
instant, the app calls Make through a webhook the moment the status changes.
When to use it
to tag the contact as away in your CRM, so nobody pushes a deal forward while the decision maker is out.
Watch out
manual status changes also fire it, so a teammate cleaning up statuses can start a burst of runs.
Woodpecker6Watch Prospect Blacklisted

Watch Prospect Blacklisted

Instant trigger

In Make“Triggers when prospect unsubscribe or when it is marked as 'Blacklist'.”

When a prospect unsubscribes or is marked Blacklist, Make gets the contact right away, so the opt-out can travel to every tool that might email them again.

How it fires
instant, Woodpecker sends the event to Make by webhook as soon as it is recorded.
When to use it
to add the address to a suppression list in your newsletter tool or to flag it in your CRM, keeping all your sending consistent with the prospect's choice.
Watch out
this trigger only reports the change; your scenario must do the actual removal in the other tools.
Woodpecker7Watch Prospect Bounced

Watch Prospect Bounced

Instant trigger

In Make“Triggers when your email was bounced and a prospect is marked as ‘Bounced’.”

You get each prospect whose email bounced and who is now marked Bounced, so a dead address stops polluting your other databases too.

How it fires
instant, the bounce reaches Make through a webhook as soon as Woodpecker flags it.
When to use it
to mark the contact for research in your CRM, so someone looks for a working address instead of the rep sending into the void.
Watch out
pair it with Delete a Prospect only if you are sure; a deleted prospect cannot be restored from the scenario.
Woodpecker8Watch Prospect Interested

Watch Prospect Interested

Instant trigger

In Make“Triggers when a prospect is marked as ‘Interested’.”

The best news in a campaign reaches your team at once: when a prospect is marked Interested, Make receives it and can hand the lead to whoever closes deals.

How it fires
instant, Woodpecker calls Make through a webhook as soon as the status is set.
When to use it
to create a deal in your CRM and post the name in a sales channel, so a warm lead gets an answer while the conversation is still alive.
Watch out
the status has to be set in Woodpecker first; a reply that nobody marks will not reach this trigger.
Woodpecker9Watch Prospect Invalid

Watch Prospect Invalid

Instant trigger

In Make“Triggers when the prospect's email address is marked as ‘Invalid’.”

This one reports prospects whose email address has been marked Invalid, which lets you fix the data at its source instead of in Woodpecker alone.

How it fires
instant, a webhook carries the event to Make as soon as the address is flagged.
When to use it
when leads come from a form or an enrichment tool, to send the bad address back there and see where wrong data enters your pipeline.
Watch out
invalid differs from bounced; if you want both cases, build one scenario per trigger or route them into the same follow-up.
Woodpecker10Watch Prospect Maybe Later

Watch Prospect Maybe Later

Instant trigger

In Make“Triggers when a prospect is marked as ‘Maybe later’.”

A prospect who says not now is still a lead. When someone is marked Maybe later, Make receives the contact so it can go into a nurture track rather than disappear.

How it fires
instant, Woodpecker notifies Make through a webhook as soon as the status is set.
When to use it
to move the contact into a newsletter list or a CRM stage reserved for later conversations.
Watch out
the status comes from Woodpecker, so the trigger only works if your team actually marks these answers instead of leaving them as plain replies.
Woodpecker11Watch Prospect Not Interested

Watch Prospect Not Interested

Instant trigger

In Make“Triggers when a prospect is marked as ‘Not interested’.”

Declined prospects get recorded too: when a contact is marked Not interested, Make receives it and can close the loop in your other tools.

How it fires
instant, the app calls Make by webhook right when the status changes.
When to use it
to close the matching deal as lost in your CRM, so pipeline reports reflect what really happened in the campaign.
Watch out
not interested is not an unsubscribe; if the prospect asked to stop receiving emails, Watch Prospect Blacklisted is the trigger that covers it.
Woodpecker12Watch Prospect Reply

Watch Prospect Reply

Instant trigger

In Make“Triggers when a prospect replies or their status is manually changed to "Replied".”

Any answer from a prospect starts your scenario, whether they replied themselves or someone set their status to Replied by hand. It is the widest net for conversations that need a human.

How it fires
instant, Woodpecker sends the reply event to Make through a webhook as soon as it happens.
When to use it
to alert the owner of the account in chat, or to open a follow-up task, when you do not want to wait for someone to qualify the reply.
Watch out
it also catches negative answers; filter on the status if only positive replies should go further.
Modules

What can Make do in Woodpecker?

Woodpecker gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Woodpecker1

Add Prospects to a Campaign

Action

In Make“Adds prospects to the selected campaign.”

This action puts prospects into the campaign you select, so they start receiving its sequence without anyone opening Woodpecker.

When to use it
right after Create a Prospect, or when a contact reaches a stage in your CRM that calls for a specific outreach.
Watch out
it places prospects that already exist in Woodpecker, so put Create a Prospect or Search Prospects in front of it.
Woodpecker2

Create a Prospect

Action

In Make“Creates an array of new prospects.”

New contacts from any other app become Woodpecker prospects, one bundle at a time or as a batch, since the module accepts several prospects in one go.

When to use it
when leads come from a form, a spreadsheet or an enrichment tool and you want them in Woodpecker without exporting a file.
Watch out
creating a prospect does not add it to a campaign; chain Add Prospects to a Campaign after it.
Woodpecker3

Delete a Prospect

Action

In Make“Deletes an existing prospect.”

This removes an existing prospect from Woodpecker for good, which helps when a contact must disappear from your outreach data entirely.

When to use it
when a data deletion request arrives, or at the end of a clean-up scenario that has already checked the contact.
Watch out
no module in the list brings a deleted prospect back; test it with Run once on a dummy prospect before letting it run on real data.
Woodpecker4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the listed modules does what you need, this one calls any endpoint of the Woodpecker API with the same connection, so you never have to handle the key twice.

When to use it
for campaign data or any Woodpecker feature that the ready-made modules leave out.
Watch out
you write the request yourself, so keep the Woodpecker API documentation open while you fill it; the Make troubleshooting guide helps when a call fails.
Woodpecker5

Update Prospects

Action

In Make“Updates an array of existing prospects by ID.”

Change details on prospects that already exist, identified by their ID, so Woodpecker keeps up with what your CRM or your team learns about them.

When to use it
when a contact changes company or title in your CRM and the next email should use the new information.
Watch out
the module works by ID, so put Search Prospects in front of it when you only have an email address.
Woodpecker6

Search Prospects

Search

In Make“Searches for a specific user or lists them all.”

Look up one prospect or pull the whole list, then use what comes back in the next modules. A search can return zero, one or many bundles.

When to use it
to find a prospect's ID before Update Prospects or Delete a Prospect, or to check whether a lead is already in Woodpecker before creating it.
Watch out
every bundle returned runs the following modules once, so an empty search stops the flow and a broad one multiplies operations.
Need help

Need help automating Woodpecker with Make?

A person reads every message.

FAQ

Woodpecker and Make: common questions

01Is the Woodpecker Make integration free?
Yes, on Make's side. Woodpecker is a standard app, available from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits per month. You still need your own Woodpecker subscription, which Make does not cover.
02What do you need to connect Woodpecker to Make?
You need an active Woodpecker account and an API key. In Woodpecker, go to Settings, open the API Key tab, click Generate API Key and copy the key. In Make, add a Woodpecker module, click Create a connection, give it a name if you like, and paste the key. For a trigger, click Create a webhook first, then create the connection inside it. The connection is then reused by every Woodpecker module in your scenarios.
03Do Woodpecker triggers in Make fire in real time?
Yes. All 12 Woodpecker triggers are instant: Woodpecker calls Make through a webhook as soon as the event happens, whether it is an open, a click, a reply, a bounce or a status change. You do not wait for the 15 minute schedule that applies to scheduled triggers in other apps. Each trigger needs its webhook, which Make creates when you click Create a webhook while adding the module, so keep that button in mind on your first trigger.
04What if the Woodpecker module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Woodpecker API with the connection you already set up, which covers what the listed actions leave aside, as they only deal with prospects and campaign membership. The Woodpecker documentation in Make lists no specific limit beyond a warning that its content was generated from vendor documentation and may contain mistakes, so check important details with Woodpecker directly before you rely on them.
05Should you use Make or n8n for Woodpecker?
It depends on the tool your team already uses. In Make, Woodpecker comes with 18 modules: 12 instant triggers, 5 actions and 1 search, plus Make an API Call for the rest, and it works from the Free plan. Many apps also have a node in n8n, so check what the n8n node for Woodpecker covers before choosing. Compare the events and actions each side offers against the scenario you want to build.
Same platform

Other docs you might need on this stack.

Browse all integrations