Can OpenPhone and AMPECO talk in both directions?

Yes. Build one flow that starts in OpenPhone and acts in AMPECO, 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 OpenPhone to AMPECO

Move data between OpenPhone and AMPECO 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 OpenPhone Explore AMPECO

OpenPhone triggers: 5
OpenPhone actions: 4
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with OpenPhone and AMPECO

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

Call Recording Completed in OpenPhone creates Custom API Call in AMPECO
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
New notification in AMPECO creates Send Message in OpenPhone
Triggers when a webhook notification event is received from Ampeco
Call Recording Completed in OpenPhone creates Actions - Charge Point - Change Availability in AMPECO
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
New notification in AMPECO creates Create Contact in OpenPhone
Triggers when a webhook notification event is received from Ampeco
Call Recording Completed in OpenPhone creates Actions - Charge Point - Change Owner in AMPECO
Fires when a call recording finishes. Useful for post-transcription or archival workflows.
New notification in AMPECO creates Update Contact in OpenPhone
Triggers when a webhook notification event is received from Ampeco