Cold email automation tool for sales teams to send personalized outreach campaigns
Woodpecker currently provides 20 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Prospect Replied
Triggers when a prospect replies to an email or their status is manually set to RESPONDED
Prospect Blacklisted
Triggers when a prospect is added to the blacklist
Prospect Opt-out
Triggers when a prospect opts out from receiving emails
Prospect Bounced
Triggers when an email to a prospect bounces
Prospect Invalid
Triggers when a prospect email is marked as invalid
Prospect Autoreplied
Triggers when an autoreply is detected from a prospect
Prospect Saved
Triggers when a prospect is saved
Prospect Nonresponsive
Triggers when a prospect is marked as nonresponsive
Prospect Clicked a Link
Triggers when a prospect clicks a link in an email
Prospect Opened an Email
Triggers when a prospect opens an email
Prospect Interested
Triggers when a prospect is marked as interested
Prospect Maybe Later
Triggers when a prospect is marked as maybe later
Prospect Not Interested
Triggers when a prospect is marked as not interested
Campaign Email Sent
Triggers when a campaign email is sent to a prospect
Follow-up After Autoreply
Triggers when a follow-up is scheduled after an autoreply
Secondary Replied
Triggers when a secondary email address replies
Campaign Completed
Triggers when a campaign is completed
Task Created
Triggers when a task is created
Task Done
Triggers when a task is marked as done
Task Ignored
Triggers when a task is ignored
Create/Update Prospect in Campaign
Adds a new prospect or updates existing prospect data in a campaign
Create/Update Prospect
Adds a new prospect or updates existing prospect in the global prospect list
Blacklist Domain
Add a domain to the blacklist to block sending to all prospects within that domain
Get Prospect Responses
Fetch all responses from a specified prospect
Find Prospect by Email
Search for a prospect by their email address
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Woodpecker event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Prospect Replied
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Woodpecker action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create/Update Prospect in Campaign
Combine Woodpecker with another integration and Coherence records to keep account, contact, and deal context attached to the work around it.
Starts with
Prospect Replied
Finishes with
Create/Update Prospect in Campaign, then preserve the outcome in Coherence
The exact authentication fields depend on Woodpecker. The workflow structure stays straightforward:
Authorize the Woodpecker account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Woodpecker or provide a complementary trigger or action.
Woodpecker currently provides 20 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to keep account, contact, and deal context attached to the work around it.
Woodpecker currently lists 20 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Woodpecker triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
