Can Respond.io and AMPECO talk in both directions?

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

Move data between Respond.io 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 Respond.io Explore AMPECO

Respond.io triggers: 7
Respond.io actions: 9
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with Respond.io and AMPECO

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

Contact Tag Updated in Respond.io creates Custom API Call in AMPECO
Triggers when a tag is added or removed from a contact in Respond.io.
New notification in AMPECO creates Add Comment to Conversation in Respond.io
Triggers when a webhook notification event is received from Ampeco
Contact Tag Updated in Respond.io creates Actions - Charge Point - Change Availability in AMPECO
Triggers when a tag is added or removed from a contact in Respond.io.
New notification in AMPECO creates Add Tag to Contact in Respond.io
Triggers when a webhook notification event is received from Ampeco
Contact Tag Updated in Respond.io creates Actions - Charge Point - Change Owner in AMPECO
Triggers when a tag is added or removed from a contact in Respond.io.
New notification in AMPECO creates Assign or Unassign Conversation in Respond.io
Triggers when a webhook notification event is received from Ampeco