Can Woodpecker and NinjaPipe talk in both directions?

Yes. Build one flow that starts in Woodpecker and acts in NinjaPipe, 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.

Connect Woodpecker to NinjaPipe

Move data between Woodpecker and NinjaPipe 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.

Start building Explore Woodpecker Explore NinjaPipe

Woodpecker triggers: 20
Woodpecker actions: 6
NinjaPipe triggers: 8
NinjaPipe actions: 51

Automation ideas

What you can build with Woodpecker and NinjaPipe

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

Prospect Replied in Woodpecker creates Create Contact in NinjaPipe
Triggers when a prospect replies to an email or their status is manually set to RESPONDED
New Contact in NinjaPipe creates Create/Update Prospect in Campaign in Woodpecker
Triggers when a new contact is created.
Prospect Replied in Woodpecker creates Update Contact in NinjaPipe
Triggers when a prospect replies to an email or their status is manually set to RESPONDED
New Contact in NinjaPipe creates Create/Update Prospect in Woodpecker
Triggers when a new contact is created.
Prospect Replied in Woodpecker creates Get Contact in NinjaPipe
Triggers when a prospect replies to an email or their status is manually set to RESPONDED
New Contact in NinjaPipe creates Blacklist Domain in Woodpecker
Triggers when a new contact is created.