Skip to content
OpenPhone logoMoxie logo

Connect OpenPhone to Moxie

Move data between OpenPhone 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.

OpenPhone triggers
5
OpenPhone actions
4
Moxie triggers
22
Moxie actions
12

Automation ideas

What you can build with OpenPhone and Moxie

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

  • Call Recording Completed in OpenPhone creates Create a Client in Moxie

    Fires when a call recording finishes. Useful for post-transcription or archival workflows.

  • Client Created in Moxie creates Send Message in OpenPhone

    Triggered when a new client is created.

  • Call Recording Completed in OpenPhone creates Create a Contact in Moxie

    Fires when a call recording finishes. Useful for post-transcription or archival workflows.

  • Client Created in Moxie creates Create Contact in OpenPhone

    Triggered when a new client is created.

  • Call Recording Completed in OpenPhone creates Create a Task in Moxie

    Fires when a call recording finishes. Useful for post-transcription or archival workflows.

  • Client Created in Moxie creates Update Contact in OpenPhone

    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 OpenPhone 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.