Skip to content
OpenPhone logoWedof logo

Connect OpenPhone to Wedof

Move data between OpenPhone and Wedof 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
Wedof triggers
28
Wedof actions
45

Automation ideas

What you can build with OpenPhone and Wedof

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

  • Call Recording Completed in OpenPhone creates Lister les statistiques des partenaires in Wedof

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

  • Nouveau dossier de formation in Wedof creates Send Message in OpenPhone

    Se déclenche lorsqu'un nouveau dossier de formation est créé (non traité)

  • Call Recording Completed in OpenPhone creates Récupérer un dossier de formation in Wedof

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

  • Nouveau dossier de formation in Wedof creates Create Contact in OpenPhone

    Se déclenche lorsqu'un nouveau dossier de formation est créé (non traité)

  • Call Recording Completed in OpenPhone creates Rechercher un ou plusieurs dossiers de formation in Wedof

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

  • Nouveau dossier de formation in Wedof creates Update Contact in OpenPhone

    Se déclenche lorsqu'un nouveau dossier de formation est créé (non traité)

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