Can Ninox and AMPECO talk in both directions?

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

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

Ninox triggers: 1
Ninox actions: 8
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with Ninox and AMPECO

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

New Record in Ninox creates Custom API Call in AMPECO
Triggers when a new record is created in a table.
New notification in AMPECO creates Create Record in Ninox
Triggers when a webhook notification event is received from Ampeco
New Record in Ninox creates Actions - Charge Point - Change Availability in AMPECO
Triggers when a new record is created in a table.
New notification in AMPECO creates Update Record in Ninox
Triggers when a webhook notification event is received from Ampeco
New Record in Ninox creates Actions - Charge Point - Change Owner in AMPECO
Triggers when a new record is created in a table.
New notification in AMPECO creates Delete Record in Ninox
Triggers when a webhook notification event is received from Ampeco