Skip to content
OpenPhone logo0CodeKit logo

Connect OpenPhone to 0CodeKit

Move data between OpenPhone and 0CodeKit 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
0CodeKit triggers
0
0CodeKit actions
34

Automation ideas

What you can build with OpenPhone and 0CodeKit

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

  • Call Recording Completed in OpenPhone creates Current Month in 0CodeKit

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

  • Call Recording Completed in OpenPhone creates Specific Month and Year in 0CodeKit

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

  • Call Recording Completed in OpenPhone creates Current Week in 0CodeKit

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

  • Outgoing Message Delivered in OpenPhone creates Current Month in 0CodeKit

    Fires when an outbound message is delivered successfully. Useful for message confirmation workflows.

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 0CodeKit, 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.