Can Pubrio and AMPECO talk in both directions?

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

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

Pubrio triggers: 1
Pubrio actions: 28
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with Pubrio and AMPECO

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

Monitor Event (Webhook) in Pubrio creates Custom API Call in AMPECO
Triggers once per signal (signal_first mode) or once per company (company_first mode) when a Pubrio monitor fires. Copy the webhook URL into your Pubrio monitor destination configuration.
New notification in AMPECO creates Search Companies in Pubrio
Triggers when a webhook notification event is received from Ampeco
Monitor Event (Webhook) in Pubrio creates Actions - Charge Point - Change Availability in AMPECO
Triggers once per signal (signal_first mode) or once per company (company_first mode) when a Pubrio monitor fires. Copy the webhook URL into your Pubrio monitor destination configuration.
New notification in AMPECO creates Lookup Company in Pubrio
Triggers when a webhook notification event is received from Ampeco
Monitor Event (Webhook) in Pubrio creates Actions - Charge Point - Change Owner in AMPECO
Triggers once per signal (signal_first mode) or once per company (company_first mode) when a Pubrio monitor fires. Copy the webhook URL into your Pubrio monitor destination configuration.
New notification in AMPECO creates Enrich Company in Pubrio
Triggers when a webhook notification event is received from Ampeco