Can Respaid and AMPECO talk in both directions?

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

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

Respaid triggers: 10
Respaid actions: 4
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with Respaid and AMPECO

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

New Campaign Creation Result in Respaid creates Custom API Call in AMPECO
Triggers when the campaign is created.
New notification in AMPECO creates Create New Campaign in Respaid
Triggers when a webhook notification event is received from Ampeco
New Campaign Creation Result in Respaid creates Actions - Charge Point - Change Availability in AMPECO
Triggers when the campaign is created.
New notification in AMPECO creates Stop Collection for Direct Full Payment in Respaid
Triggers when a webhook notification event is received from Ampeco
New Campaign Creation Result in Respaid creates Actions - Charge Point - Change Owner in AMPECO
Triggers when the campaign is created.
New notification in AMPECO creates Stop Collection for Direct Partial Payment in Respaid
Triggers when a webhook notification event is received from Ampeco