Can Docusign and AMPECO talk in both directions?

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

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

Docusign triggers: 11
Docusign actions: 8
AMPECO triggers: 1
AMPECO actions: 377

Automation ideas

What you can build with Docusign and AMPECO

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

Signing Request Created in Docusign creates Custom API Call in AMPECO
Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.
New notification in AMPECO creates Search Signing Requests in Docusign
Triggers when a webhook notification event is received from Ampeco
Signing Request Created in Docusign creates Actions - Charge Point - Change Availability in AMPECO
Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.
New notification in AMPECO creates Get Signing Request Details in Docusign
Triggers when a webhook notification event is received from Ampeco
Signing Request Created in Docusign creates Actions - Charge Point - Change Owner in AMPECO
Triggers when a new signing request (envelope) is created in DocuSign — whether sent immediately or saved as a draft.
New notification in AMPECO creates Download Document from Signing Request in Docusign
Triggers when a webhook notification event is received from Ampeco