Can ConnectUC and AMPECO talk in both directions?

Yes. Build one flow that starts in ConnectUC 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 ConnectUC to AMPECO

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

ConnectUC triggers: 8
ConnectUC actions: 6
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with ConnectUC and AMPECO

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

New Recording in ConnectUC creates Custom API Call in AMPECO
Triggers when a new call recording is available
New notification in AMPECO creates Create Contact in ConnectUC
Triggers when a webhook notification event is received from Ampeco
New Recording in ConnectUC creates Actions - Charge Point - Change Availability in AMPECO
Triggers when a new call recording is available
New notification in AMPECO creates Set Do Not Disturb in ConnectUC
Triggers when a webhook notification event is received from Ampeco
New Recording in ConnectUC creates Actions - Charge Point - Change Owner in AMPECO
Triggers when a new call recording is available
New notification in AMPECO creates Find CDR in ConnectUC
Triggers when a webhook notification event is received from Ampeco