Can Hunter and NinjaPipe talk in both directions?

Yes. Build one flow that starts in Hunter 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 Hunter to NinjaPipe

Move data between Hunter 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 Hunter Explore NinjaPipe

Hunter triggers: 1
Hunter actions: 9
NinjaPipe triggers: 8
NinjaPipe actions: 51

Automation ideas

What you can build with Hunter and NinjaPipe

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

New Lead in Hunter creates Create Contact in NinjaPipe
Fires when a new lead is created.
New Contact in NinjaPipe creates Add Recipients in Hunter
Triggers when a new contact is created.
New Lead in Hunter creates Update Contact in NinjaPipe
Fires when a new lead is created.
New Contact in NinjaPipe creates Count Emails in Hunter
Triggers when a new contact is created.
New Lead in Hunter creates Get Contact in NinjaPipe
Fires when a new lead is created.
New Contact in NinjaPipe creates Create Lead in Hunter
Triggers when a new contact is created.