Can Onfleet and AMPECO talk in both directions?

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

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

Onfleet triggers: 18
Onfleet actions: 33
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with Onfleet and AMPECO

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

Task Arrival in Onfleet creates Custom API Call in AMPECO
Triggers when a task worker arriving at or closer than threshold value provided, in meters
New notification in AMPECO creates Create Recipient in Onfleet
Triggers when a webhook notification event is received from Ampeco
Task Arrival in Onfleet creates Actions - Charge Point - Change Availability in AMPECO
Triggers when a task worker arriving at or closer than threshold value provided, in meters
New notification in AMPECO creates Update Recipient in Onfleet
Triggers when a webhook notification event is received from Ampeco
Task Arrival in Onfleet creates Actions - Charge Point - Change Owner in AMPECO
Triggers when a task worker arriving at or closer than threshold value provided, in meters
New notification in AMPECO creates Get Recipient in Onfleet
Triggers when a webhook notification event is received from Ampeco