Skip to content
Woodpecker logoVillage logo

Connect Woodpecker to Village

Move data between Woodpecker and Village the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Woodpecker triggers
20
Woodpecker actions
6
Village triggers
0
Village actions
40

Automation ideas

What you can build with Woodpecker and Village

A few flows teams run between Woodpecker and Village. Use one as a starting point, or build your own from scratch.

  • Prospect Replied in Woodpecker creates Get App Information in Village

    Triggers when a prospect replies to an email or their status is manually set to RESPONDED

  • Prospect Replied in Woodpecker creates Check Company Paths in Village

    Triggers when a prospect replies to an email or their status is manually set to RESPONDED

  • Prospect Replied in Woodpecker creates Refresh Companies in Village

    Triggers when a prospect replies to an email or their status is manually set to RESPONDED

  • Prospect Blacklisted in Woodpecker creates Get App Information in Village

    Triggers when a prospect is added to the blacklist

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Woodpecker and acts in Village, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.