Skip to main content

Make Waves ’26. Find out everything we’ve announced to build a more transparent future for AI agents in business

Read now (opens in a new tab)
Woodpecker
Webflow

Connect Woodpecker and Webflow integrations

Explore ready-made Woodpecker and Webflow templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Woodpecker with Webflow and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Woodpecker
Trigger: Watch Email Opened
Webflow
Action: Select an action
1. Select a trigger

  • Triggers when a prospect opens your email (for the first time).

  • Triggers when Woodpecker sends email to particular prospect .

  • Triggers when you get an auto-reply and you set a date to resume follow-ups.

  • Triggers when a prospect clicks on a link in your email.

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

  • Triggers when prospect unsubscribe or when it is marked as 'Blacklist'.

  • Triggers when your email was bounced and a prospect is marked as ‘Bounced’.

  • Triggers when a prospect is marked as ‘Interested’.

  • Triggers when the prospect's email address is marked as ‘Invalid’.

  • Triggers when a prospect is marked as ‘Maybe later’.

  • Triggers when a prospect is marked as ‘Not interested’.

  • Triggers when a prospect replies or their status is manually changed to "Replied".

2. Select an action

  • Creates a new product item.

  • Creates an asset folder within a given site.

  • Creates a new item for a collection.

  • Deletes an existing asset.

  • Deletes an existing item for a collection.

  • Gets details of a collection.

  • Retrieves a comment thread based on the mapped ID. Use the List Comment Thread Replies module to output the replies.

  • Returns information about a given form.

  • Returns information about a given form submission.

  • Returns metadata information for a single page.

  • Gets detail of an existing product.

  • Get details of a specific site by ID.

  • Gets details about a specific asset folder.

  • Returns the details of an item by ID.

  • Gets the current inventory levels for a particular SKU item.

  • Gets details of an existing order.

  • Performs an arbitrary authorized API call.

  • Mark an order status as fulfilled, unfulfilled or refunded.

  • Publishes an existing site.

  • Publishes an existing collection item.

  • Updates hidden fields on a form submission.

  • Updates an existing product.

  • Updates an existing product SKU.

  • Updates an existing item for a collection.

  • Updates the current inventory levels for a particualr SKU item.

  • Updates an order.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Woodpecker and Webflow.

Add Prospects to a Campaign
Adds prospects to the selected campaign.
Action
Create a Product
Creates a new product item.
Action
Create a Prospect
Creates an array of new prospects.
Action
Create an Asset Folder
Creates an asset folder within a given site.
Action
Create an Item
Creates a new item for a collection.
Action
Delete a Prospect
Deletes an existing prospect.
Action
Delete an Asset
Deletes an existing asset.
Action
Delete an Item
Deletes an existing item for a collection.
Action
Get a Collection
Gets details of a collection.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.