Can DIMO and AMPECO talk in both directions?

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

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

DIMO triggers: 9
DIMO actions: 38
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with DIMO and AMPECO

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

Battery is Charging Trigger in DIMO creates Custom API Call in AMPECO
Triggers when vehicle battery charging status changes (True/False).
New notification in AMPECO creates Attestation : Create VIN VC in DIMO
Triggers when a webhook notification event is received from Ampeco
Battery is Charging Trigger in DIMO creates Actions - Charge Point - Change Availability in AMPECO
Triggers when vehicle battery charging status changes (True/False).
New notification in AMPECO creates Device Definitions : Decode VIN in DIMO
Triggers when a webhook notification event is received from Ampeco
Battery is Charging Trigger in DIMO creates Actions - Charge Point - Change Owner in AMPECO
Triggers when vehicle battery charging status changes (True/False).
New notification in AMPECO creates Device Definitions : Lookup in DIMO
Triggers when a webhook notification event is received from Ampeco