Skip to content
Woodpecker logoMoxie logo

Connect Woodpecker to Moxie

Move data between Woodpecker and Moxie 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
Moxie triggers
22
Moxie actions
12

Automation ideas

What you can build with Woodpecker and Moxie

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

  • Prospect Replied in Woodpecker creates Create a Client in Moxie

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

  • Client Created in Moxie creates Create/Update Prospect in Campaign in Woodpecker

    Triggered when a new client is created.

  • Prospect Replied in Woodpecker creates Create a Contact in Moxie

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

  • Client Created in Moxie creates Create/Update Prospect in Woodpecker

    Triggered when a new client is created.

  • Prospect Replied in Woodpecker creates Create a Task in Moxie

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

  • Client Created in Moxie creates Blacklist Domain in Woodpecker

    Triggered when a new client is created.

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 Moxie, 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.